Thoughtful perspectives, practical frameworks, and expert takes on giving every team and AI assistant trusted answers from enterprise data.
A replicated Banner lands every column and 99 correct foreign keys on the student record, and still cannot say how many students are in each major. The semantic model chooses the in-force row.
Every foreign key in a replicated ServiceTitan schema is correct, and the obvious join still credits each technician the whole ticket. The semantic model is where the split weight gets applied.
Toast stamps every order with the business day its own reports use, then leaves the rule that computed it on an endpoint the connector never calls. The semantic model makes it the only day grain.
Every Shopify money field lands twice, once in your store's currency and once in whatever currency each customer paid in. The semantic model binds revenue to one and refuses to sum the other.
QuickBooks Online Advanced lets you configure twelve custom fields per form. The REST API returns three. The semantic model records which three, and fails loudly on the nine that never arrive.
A HubSpot deal has no company column. The link lives in a bridge table that repeats per association type, so pipeline by account double counts. The semantic model declares the primary association.
Every code field on the opportunity lands as an integer, and the labels live in a stringmap the connector cannot decode. The semantic model is where Won stops meaning three different things.
Fivetran's Acumatica connector lands 19 tables and no Attribute values, so the fields the business asks about are not in the warehouse copy. What a semantic model can recover, and what it cannot.
Procore hands you custom_fields as a JSON blob keyed by integers. The label your team picked is nowhere in the warehouse copy. The semantic model is where that id gets bound back to its meaning.
Business Central shows eight dimension columns on the G/L Entries page. Six are computed on read, so only two survive replication. The semantic model resolves the rest through the dimension set.
Sage Intacct's product is its dimensions, and none of them lands as a table. Every dimension question bins on a string that drifts on rename, until the semantic model binds it to the id instead.
Customer Request Type is not a column on issue. It lives under a customfield id that differs per instance, so the obvious grouping returns three buckets. Bind the id once in the semantic model.