5001 to COGS.
Choose a direction
Mappings only go one way: pick the shared, canonical Dimension as the target, and map each source Dimension into it. If you have GL accounts from two different entities that need to land in the same reporting structure, map each entity’s Account Dimension into the same target separately — don’t try to map the target back to a source, since a mapping that creates a cycle is refused.Create a mapping
Ask Ari to map specific items, for example, “Map account 5001 to COGS and 6001 to Payroll.” A rule for an item that already has a mapping updates that item’s existing rule.When a plain pair isn’t enough
Some rows need a real condition instead of a simple equality, like a set of accounts (“8001 or 8002 maps to Other Income”) or a rule that spans more than one key at once. Ask Ari to write these as a condition instead of a pair; Ari carries this through into the same formula-style logic used elsewhere in the Model.Set a catch-all
Every target Dimension can have one catch-all: the target item used when no explicit mapping rule matches. Ask Ari to set or clear it. Without a catch-all, an unmatched source item remains unmapped.Remove mappings
Ask Ari to:- Unmap specific rows, leaving the rest of the lookup untouched.
- Remove an entire lookup when a source stops feeding into a target altogether.