Skip to main content

CryspIQ® v3.3.0

Release Date: October 2026

This release changes when a mapping (data-quality) exception closes automatically, scopes dimension business keys by company, and asks Guided Setup for each file’s own record ID.

Mapping exceptions close only on a trusted record ID​

Exceptions now close automatically only when the source record has a trusted record ID (a flagged own-ID column).

  • Activity maps whose LinkKey is a person key — including all Guided Setup activity maps created before this release — no longer auto-close. Stewards close those exceptions, or re-run Guided Setup and flag the activity’s own ID column.
  • A message that has ever had a People or Company map never auto-closes its activity exceptions by LinkKey.
  • A LinkKey produced by a method or a default is never trusted.
  • Replays of identical files refresh the existing exception rather than adding a duplicate.

Steward steps and Issue-panel provenance are in Mapping exceptions.

What’s new in mapping​

A dimension business key belongs to one company inside a client warehouse. DW.Load timelines, DW.Lookup and IQ.Map lookups are scoped by that company. Clients that already have a single company see no behaviour change.

Guided Setup now asks:

  • People/Company files: “What identifies each record?”
  • Activity files: “Which column is each activity’s own ID?”

Reference-named columns (InvoiceNumber, OwnerId, …) are never auto-picked as the record ID.

Parking Lot​

A corrected value re-sent on the same link key and date is kept alongside the original, matching the fact loads. Healing scans each fact table once per run. See the Parking Lot guide.

Who this is for​

Data stewards​

  • Exceptions you used to see close on replay may stay open until you flag the activity’s own ID or close them.
  • The Issue panel shows the source record, identity basis, times seen and files for rows loaded after this change.

Administrators​

  • Deploy order for other environments is Web API then IQ.Map then React, after any provenance-column script named on the work item.
  • No warehouse schema change is required for the company-scoped key work when the client has one company.