Skip to main content

Mapping exceptions

Mapping exceptions (data-quality issues raised when a record cannot be mapped) close automatically only when the record has a trusted record ID — a column flagged as that file’s own ID. That is the AB#2073 Phase 0 change this page describes.

info

A LinkKey that is a person key is not a trusted record ID. Replaying a file does not close those exceptions.

What closes automatically​

An open exception is closed by a later load only when IQ.Map can trust the source record’s own ID:

  • The column is flagged as the record ID (Guided Setup’s “own ID”, or the source-tag primary-key flag).
  • A LinkKey produced by a method or a default is never trusted.
  • A message that has ever had a People or Company (dimension) map never auto-closes its activity exceptions by LinkKey. The LinkKey on those activities is the person or organisation, not the activity.

What a steward must close​

These exceptions stay open until a steward marks them resolved:

  • Activity maps whose LinkKey is a person key. This includes every Guided Setup activity map created before this release. Re-run Guided Setup and flag the activity’s own ID column, or close the exceptions yourself.
  • Records with no flagged own-ID column. Activity files without an ID now key facts with an R: LinkKey built from the row hash; stewards close those exceptions.
  • A LinkKey built by a method or a default.

Identical replays​

When the same record is sent again, the existing open exception is refreshed (times seen, last seen, last file). A new exception row is not added. Full replay identity is a later phase; this refresh is the Phase 0 behaviour.

Rows from before this change have no provenance on the Issue panel. On first replay, some legacy open rows are not adopted — the steward should close the leftover legacy row when a new row appears beside it.

What Guided Setup asks​

  • People and Company files: What identifies each record?
  • Activity files: Which column is each activity’s own ID?
  • A reference-named column (InvoiceNumber, OwnerId, AccountId, …) is never auto-picked as the record ID. The steward can still choose it, and the wizard warns.

What’s new in mapping (company-scoped keys)​

A dimension business key (Location, Account, Asset, Entity including Person/Company, Product, Service) belongs to one company inside a client warehouse. Lookups and load timelines are scoped by company. Single-company clients see no change.

Parking Lot corrections​

A corrected value re-sent on the same link key and date is kept alongside the original, matching the fact loads. Fact counts and totals may rise, because rows that were wrongly de-duplicated now heal.