Agami Insights

query quickbooks custom fields fivetran warehouse: twelve configured on the invoice form, three returned by the REST API, and no column marking the nine that never arrived.

You Configured Twelve QuickBooks Custom Fields. Three Arrive.

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.

HubSpot duplicate deals multiple companies: deal_company is keyed on deal_id, company_id, type_id and category, so one deal on one company already lands two rows, each with the full amount

One HubSpot Deal, Three Companies, Three Rows

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.

Query Dynamics 365 Sales data with AI: the Won label the app shows and the integer 1 the warehouse lands. Every code field is an integer; labels live in stringmap.

Three Columns Mean Won. Your Semantic Model Picks One.

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.

Query Acumatica custom fields Fivetran warehouse: the Priority Tier Attribute the app shows never lands. Custom data is unchecked on the connector.

Fivetran Lands 19 Acumatica Tables and Not One Attribute

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.

Query Procore custom fields from your warehouse: what the app shows as a Risk Impact dropdown lands in the warehouse as a JSON blob whose key is an integer the reader has never seen.

The Procore Custom Field Whose Column Name Is a Number

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.

Query Business Central data with AI: eight dimension columns on the G/L Entries page in the app, two on the ledger table in the warehouse. Six of them were FlowFields, not columns.

Six of Eight Business Central Dimension Columns Are Computed on Read

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.

Query Sage Intacct data with AI: eight dimensions in the app, zero dimension tables in the warehouse. Fivetran lands two strings per row, no lookup, no hierarchy.

Sage Intacct's Dimensions Don't Land. The Semantic Model Puts Them Back.

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.

Jira service management request type reporting warehouse: Customer Request Type lives in issue_field_history under an instance-specific customfield id, not as a column on issue

Your Jira Portal Has Dozens of Request Types. Your Warehouse Has Three.

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 multi-book double counting: one transaction line posts a debit and a credit per accounting book, so a two-book estate lands four rows and revenue reads at twice the true figure

One NetSuite Dollar, Counted Twice, Until the Semantic Model Says Once

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.

ServiceNow semantic model inheritance: the same query's joins flagged undefined_relationship before, and governed after the inheritance is declared

How to Build a ServiceNow Semantic Model That Governs Inherited Tables

Declare the inheritance join and the missing company FK, sign them off, and the incidents-by-customer chain comes back governed instead of flagged.

ServiceNow incident task join: incident extends task through inheritance, so the two tables share a sys_id and no foreign key connects them

In ServiceNow, Incident and Task Are the Same Record

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.

Stopping Salesforce pipeline double counting: a proposed relationship moving from unreviewed to approved with a sign-off block that records the grain

How to Build a Salesforce Semantic Model That Can't Double-Count Your Pipeline

A four-step walkthrough on replicated Salesforce: introspect the schema, correct the grain and the custom fields, sign the definitions off, then verify the breakdown ties to the total.