Skip to main content
Something's wrong

Correcting a mapping or field value

Understand the difference between a one-off value fix and a mapping change, and know who makes which.

The short answer

There are two kinds of data error. A one-off value error affects a single event because of something that happened in the source system for that event: you fix the value in the Control Panel and resend. A mapping error means the transformation logic is consistently producing the wrong output across many events: the transformation itself has to change. An Owner can make that change in the Control Panel, or you can ask HC to make it.

How it works

A one-off value error

A specific event has an incorrect value because of something that happened in the source system for that particular event (for example, a customer entered an invalid postcode, or a product was missing a required field). You fix the value in the Control Panel for that event and resend it.

A mapping error

The transformation logic is consistently producing the wrong output across multiple events (for example, a tax amount is being mapped to the wrong ERP field). Fixing it means changing the transformation. Owners can create and edit transformations in the Control Panel and test a change against real data before saving it. Ask HC to make the change instead when it affects live order flows or financial postings, or when you would rather it was scoped and signed off first.

Why the distinction matters

If the same field is wrong across multiple events, fixing and resending individual events does not help: you will be correcting the same field by hand every time, and the next event will be wrong again. Correct the transformation first, then resend the affected events so they run through the corrected logic.

What this means for you

  • One event with a wrong value: fix it in the Control Panel and resend. See How to fix and resend a failed event.

  • The same field wrong across multiple events: do not fix and resend the events one by one. Change the transformation. An Owner can do this in the Control Panel and test it first: see Testing a transformation change before you save it.

  • If you would rather HC made the change, or it affects live order flows or financial postings, contact HC with the stream, the field that is incorrect, the value it is currently producing, what it should produce, and a sample event ID.

  • Once the corrected transformation is live, whoever made the change, bulk-resend the affected events if needed. See Requesting a bulk resend.

Doing this yourself

Fixing a one-off value error

  1. Find the failed event in the Control Panel.

  2. Open the event and click Fix and resend.

  3. Find the incorrect field and correct the value.

  4. Click Resend.

See How to fix and resend a failed event for full steps.

Changing the transformation yourself

  1. Copy an example payload from an event that has run through the stream.

  2. Open the transformation from Transformations and edit it.

  3. Run your example through Preview output, and check the diff under Review changes.

  4. Save with Update Transformation.

  5. Resend the affected events so they run through the corrected logic.

See Testing a transformation change before you save it for full steps.

Asking HC to make the change

  1. Identify the stream, the field that is incorrect, what value it is currently producing, and what it should produce.

  2. Contact HC with this information and include a sample event ID.

  3. HC will make the change.

  4. Once HC confirms the fix is live, bulk-resend affected events if needed (see Requesting a bulk resend).

Related

Was this helpful?

Still need help? Ask the team