NCR Counterpoint to iPaaS.com Product Substitute Item Mapping Documentation

Summary

This mapping collection removes a substitute item relationship from iPaaS.com when the corresponding relationship has been removed in NCR Counterpoint. A substitute item in Counterpoint is a relationship between two products — the item, and the product that may be supplied in its place. iPaaS.com holds these as related products.

ID Format

Manual Sync id: the relationship's Counterpoint identity — the item number and the substitute item number, joined by a pipe. This collection reads inbound from Counterpoint, so the id entered on the Manual Sync page is built from Counterpoint-side values, not iPaaS.com ones.
External ID saved after transfer: when a substitute item relationship was first transferred, iPaaS.com recorded that same Counterpoint identity as the external ID on a dedicated platform-managed external-ID record. That record — not any field on the related-product record itself — is the primary match, and it is how this collection resolves which record to remove. Because the identity is made up of both products, it names one specific substitution rather than the item's substitutions as a group.

Deleted Record Support

Deletions are carried by the Delete NCR Counterpoint Product Substitute Item TO iPaaS.com collection: when the record is removed in Counterpoint, that collection sends the removal to iPaaS.com. Whether the removal transfers automatically depends on the delete trigger event being available; where it is not, the collection runs through Manual Sync. See NCR Counterpoint Known Limitations.

Mapping Collection Status

Status: Enabled. No mapping filter is applied.
Trigger Events: see Transfer Methods in the collection description; automatic transfers require the relevant Outbound/Inbound Data Flow subscriptions to be enabled.

Duplicate or Conflicting Mappings

Add/Update NCR Counterpoint Product Substitute Item TO iPaaS.com: creates and maintains the substitute item relationships this collection removes. It operates on the same entity, but reaches iPaaS.com by a different route — it is a child collection dispatched as part of a product's transfer, whereas this collection is standalone and runs on its own.

Important: these two collections are complementary rather than alternatives, and are normally enabled together — one puts a substitution in place, the other takes it away. Because a relationship arrives with its product but is removed only by this collection, subscribers or their MiSP should review both before enabling either, and should be aware that the two do not run on the same schedule.

System Caveats

iPaaS.com Caveats

This collection has no mappings, and is not supposed to have any: a mapping's job is to decide what value goes into a destination field, and a delete writes no fields — it removes a record iPaaS.com already holds. iPaaS.com resolves which record that is from the identity saved when the relationship was first transferred, so no mapped field is involved at any point. Subscribers or their MiSP should leave this collection empty. Adding mappings to it does not extend what the delete does.
The relationship must have been transferred before it can be removed: the delete matches on the external-ID record saved at the original transfer. A substitution that never reached iPaaS.com has no record for this collection to act on.

Integration Flow

No records are transferred as prerequisites for this collection. The records it references are expected to exist already.
The record is sent to iPaaS.com, where subsequent transfers are routed by the external ID recorded on transfer.

Mappings

Delete NCR Counterpoint Product Substitute Item TO iPaaS.com

This collection carries no mapped fields. iPaaS.com matches the record by the external ID recorded when it first transferred, so a removal needs no field mapping.

Error Handling

Errors raised while transferring these records surface at Dashboard / Integration Monitoring / Error Logs. The specific messages, their causes and their resolutions are documented in NCR Counterpoint Error Messages. A record stopped by an error is not retried automatically; it must be resolved manually.

Testing & Validation

Replace every placeholder value called out above with one from the target Counterpoint installation, and confirm each exists in Counterpoint.
Transfer a single record through Manual Sync and confirm it appears in Counterpoint as expected.
Confirm any child records transferred with the parent.
Enable the relevant triggers and confirm a new record transfers automatically, and that a change updates the same Counterpoint record rather than creating a second one.
Attempt a transfer with a missing required field and confirm the expected error appears at Dashboard / Integration Monitoring / Error Logs.

Additional Notes

Removals do not transfer on their own until the trigger is installed: at the time this documentation was written, the substitute item trigger subscriptions are not created by default. Until that Counterpoint-side installation step has been carried out and the subscriptions enabled, a substitute item relationship deleted in NCR Counterpoint remains in iPaaS.com until this collection is run on demand. Subscribers or their MiSP should either carry out that step or plan for the on-demand sync.
Validate the removal end to end before relying on it: subscribers or their MiSP should confirm in a staging environment that deleting a substitute item relationship in Counterpoint and running this collection removes the corresponding related product in iPaaS.com, before relying on the behavior in production. Any error raised during the transfer surfaces at Dashboard / Integration Monitoring / Error Logs.

These and other runtime behaviors are documented in NCR Counterpoint Known Limitations.