Skip to main content

Editing and Versioning Source Messages

A Source Message defines the structure CryspIQ® expects from a source system. Over time you may need to change it — update who owns it, change how often it loads, or change the fields it contains.

CryspIQ® treats those two kinds of change very differently:

  • Changing details about a Source Message updates it in place.
  • Changing the structure (its source tags) creates a new version of the Source Message.

This guide explains when each happens and, importantly, what happens to the maps you have already built.

Two Kinds of Edit​

You change…ExamplesWhat happens
Details onlyOwner name, owner email, system name, load frequency, business function area, display nameUpdated in place — same Source Message, no new version
StructureA new CSV with different columns, or adding / removing / renaming source tagsA new version is created

The deciding factor is always the set of source tags. If the source tags do not change, nothing is versioned — regardless of how the edit was made.

info

Source tags are the fields that make up a Source Message — for example CustomerId, CustomerName or EmailAddress. They are the structure that maps, rules and lineage all depend on.

Editing Details (In-Place Update)​

When you open a Source Message and change only its details — without uploading a new CSV — the change is saved in place.

In an in-place update:

  • The Source Message keeps the same identity.
  • Its source tags are untouched.
  • Every map built against it continues to work, unchanged.
  • No new version is created.
tip

You can safely correct an owner, update an email address or change a load frequency at any time. These edits never disturb your maps.

What Triggers a New Version​

A new version is created only when the source tags change. In practice this happens in two ways:

  1. A new CSV is uploaded with different columns. Adding, removing or renaming a column changes the source tags.
  2. The source tags are edited directly — adding, removing or renaming a tag.

Both routes are treated identically: CryspIQ® compares the new set of tag names against the current set, and versions the Source Message only if that set has changed.

note

Re-uploading a CSV with the same columns does not create a new version. Only a genuine change to the source tags rolls a version, so you are never left with unnecessary versions.

What Happens During a Version Roll​

When the structure changes, CryspIQ®:

  1. Closes the current version. The existing Source Message is retained for lineage and marked as deprecated, so data already loaded against the old structure is preserved.
  2. Creates a new version carrying the new structure.
  3. Carries your maps forward onto the new version automatically (see below).

How Your Maps Are Carried Forward​

This is the most important part of a version roll. You do not have to rebuild your maps by hand.

When a new version is created, CryspIQ® automatically recreates every map from the previous version on the new one. For each map it:

  • Recreates the map against the new version of the Source Message.
  • Re-links each field mapping to the matching source tag by name. A tag called EmailAddress on the old version is matched to EmailAddress on the new version.
  • Preserves the logic and defaults configured on each field mapping.

The result is that maps which still make sense against the new structure continue to work with no manual effort.

tip

Because tags are matched by name, keeping your source tag names stable is the single most effective way to ensure maps survive a structural change cleanly.

When the Structure Changes the Mapping​

Sometimes a structural change means a map can no longer be fully recreated — for example, a field you had mapped was removed or renamed in the new structure.

In that case CryspIQ®:

  • Carries the map forward with all the field mappings that still match.
  • Drops the field mappings whose source tag no longer exists, because there is nothing valid to link them to.
  • Highlights every impacted map so you can review and repair it.

The Review Prompt​

After you save an edit that rolled a new version and dropped one or more field mappings, CryspIQ® shows a summary listing:

  • Each map that was affected.
  • How many field mappings were dropped from it.
  • The source tags that could no longer be found.
Mappings carried forward with changes

Customer Master Map — 2 mappings dropped
  MiddleName   OldPhoneNumber

Contact Map — 1 mapping dropped
  FaxNumber
caution

Dropped field mappings are not lost data — they are mappings that referred to source tags which no longer exist. Review each highlighted map and re-point or remove the affected mappings so the map reflects the new structure.

To keep structural changes smooth:

  • Keep source tag names stable. Renaming a tag is treated as removing one and adding another, which drops any mapping that used the old name.
  • Prefer adding tags over renaming them. New tags never break existing mappings.
  • Review the summary after every version roll. If maps were impacted, repair them before relying on the new version downstream.
  • Make detail-only edits freely. Owner, email, frequency and similar changes never version or disturb your maps.

Summary​

ActionNew version?Effect on maps
Edit details only (no new CSV)NoUnchanged
Upload a new CSV with the same columnsNoUnchanged
Upload a new CSV with different columnsYesCarried forward; mappings for removed tags dropped and reported
Add, remove or rename source tagsYesCarried forward; mappings for removed tags dropped and reported
info

Versioning protects the integrity of data already loaded while letting your source structure evolve. Maps are carried forward for you, and anything that could not be carried forward cleanly is surfaced for review — so a structural change is never a silent loss of configuration.