Skip to main content
Making a change

Requesting a mapping change

How to raise a mapping change request with HighCohesion and what to expect.

When to use this

Use this guide when you need a change to your integration's transformation logic: ERP field mappings, product categorisation, tax codes, filter conditions, or how discounts are represented. Owners can make these changes themselves in the Control Panel and test them before saving — see Testing a transformation change before you save it. Raise a request with HC instead when the change affects live order flows or financial postings, when you want it scoped and tested against your data before it reaches production, or when you would rather not make the change yourself. For how your integration is put together, see How your integrations are structured and the Glossary of key terms.

The following all count as mapping changes:

  • Changing which ERP field a Shopify value maps to

  • Updating product categorisation or classification logic

  • Adjusting tax code assignments

  • Modifying filter conditions (for example which orders get synced)

  • Changing how discounts, promotions or bundles are represented in your ERP

Before you start

Have the following to hand. The more specific you are, the faster HC can scope and deliver the change.

  • Stream name: the specific integration stream affected

  • Current behaviour: what is happening now

  • Desired behaviour: what you need it to do instead

  • Sample reference: an order number, event ID or payload example that illustrates the issue. See How to find a specific event in the Control Panel

  • Deadline: if the change is time-sensitive, flag this upfront

Steps

Raise the request

  1. Contact your HighCohesion account team with the information listed above.

Work through the change with HC

  1. Agree the scope. HC confirms the scope of the change and any downstream implications.

  2. Wait for the change to be made in your test environment. HC tests against your sample data and validates the output.

  3. Complete UAT in the test environment. Allow reasonable lead time for UAT, especially if the change affects live order flows.

  4. Sign off UAT. HC deploys the change to production once UAT is signed off.

What you should see

In the test environment, the output HC validates against your sample data matches the desired behaviour you described. After you sign off UAT, the change is live in production.

If it did not work

The change is time-sensitive. Flag the deadline upfront when you raise the request, and allow for the UAT lead time.

You are not sure whether your change is a mapping change. Check it against the list under When to use this, or ask your HighCohesion account team. To contact HC, see How to get support.

How it works

The mapping logic for each stream lives in a transformation: a structured file defining how every field translates between your systems. A transformation belongs to your organisation and is visible only to your organisation. Owners can create and edit them in the Control Panel, and the editor's Preview output and Review changes tabs let you check a change against real data before you save it.

The request-and-UAT process above exists for the changes where testing in isolation is not enough. Anything that affects live order flows or financial postings is worth scoping with HC, running against your data in a test environment and signing off before it reaches production.

Related

Was this helpful?

Still need help? Ask the team