Skip to main content

NCR Counterpoint to iPaaS.com Product Variant Mapping Documentation

Field-level mapping documentation for the NCR Counterpoint Product Variant collections.

NCR Counterpoint to iPaaS.com Product Variant Mapping Documentation

Summary

This mapping collection removes a product variant from iPaaS.com when NCR Counterpoint reports that the variant has been deleted. It acts only when Counterpoint notifies iPaaS.com of that deletion. The business outcome is that a colour or size withdrawn at the till stops being offered by the systems connected to iPaaS.com, instead of lingering as a variant that can still be ordered.

Deleted Record Support

Deletions are carried by the Delete NCR Counterpoint Product Variant 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 NCR Counterpoint Product Variant TO iPaaS.com: operates on the same entity and shares the same trigger set, but carries variants into iPaaS.com rather than removing them, and is dispatched as part of the transfer of its parent collection Add/Update NCR Counterpoint Product TO iPaaS.com.

Important: this collection and Add NCR Counterpoint Product Variant TO iPaaS.com act on the same NCR Counterpoint product variants and are complementary rather than alternatives — one establishes a variant in iPaaS.com and the other removes it. Subscribers or their MiSP should review both collections' settings before enabling either, and should be aware that enabling the variant transfer without this collection means variants deleted in Counterpoint stay in iPaaS.com.

System Caveats

iPaaS.com Caveats

  • The variant must have been transferred for a delete to match: the deletion is matched to the iPaaS.com record by the Counterpoint identity saved when the variant was first transferred. A variant that was never transferred into iPaaS.com has no record to remove.

Integration Flow

  1. No records are transferred as prerequisites for this collection. The records it references are expected to exist already.

  2. The record is sent to iPaaS.com, where subsequent transfers are routed by the external ID recorded on transfer.

Mappings

Delete NCR Counterpoint Product Variant 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

  1. Replace every placeholder value called out above with one from the target Counterpoint installation, and confirm each exists in Counterpoint.

  2. Transfer a single record through Manual Sync and confirm it appears in Counterpoint as expected.

  3. Confirm any child records transferred with the parent.

  4. 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.

  5. Attempt a transfer with a missing required field and confirm the expected error appears at Dashboard / Integration Monitoring / Error Logs.

Additional Notes

  • Downstream reaction to a delete varies: at the time this documentation was written, what happens in a connected system when a variant is removed from iPaaS.com depends on that system. Subscribers should confirm in a staging environment how their downstream systems react to a variant being deleted in iPaaS.com before enabling this collection in production.

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


Related Documents

Did this answer your question?