Agami Insights

The ServiceTitan Column That Stops One Ticket Paying Two Technicians in Full

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.

Ten Date Columns on a Toast Order, and Only One Knows When Friday Ended

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.

How to Sum Shopify Revenue When Every Money Column Lands Twice

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.