Thoughtful perspectives, practical frameworks, and expert takes on giving every team and AI assistant trusted answers from enterprise data.
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.
NetSuite's reports filter the accounting line to one book automatically. The warehouse copy does not, so a naive SUM adds every dollar once per book. The semantic model is where that filter lives.
Declare the inheritance join and the missing company FK, sign them off, and the incidents-by-customer chain comes back governed instead of flagged.
Incident extends task, so the join between them is not a foreign key and introspection has nothing to infer. The semantic model is where you declare it once, for every agent.