This mapping collection brings the location groups maintained in NCR Counterpoint into iPaaS.com. It carries the group's own identifier, its readable description, and the list of locations belonging to it.

Deletions are carried by the Delete NCR Counterpoint Location Group 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.

Important: these two collections operate on the same entity and share the same trigger set. They are complementary rather than alternatives — this collection establishes and maintains the group, the other removes it — so both are normally enabled together. Subscribers or their MiSP should review both collections before enabling either, and should treat NCR Counterpoint as the source of truth for location group membership if these groups are also maintained in another connected system.

Source: LOC_GRP_ID · Destination: Name

This is a required field — iPaaS.com rejects the location group without it. The location group's own identifier in NCR Counterpoint, carried across unchanged and used as the group's name in iPaaS.com.

This is the code subscribers or their MiSP see against the group in Counterpoint, not a longer label — the readable label travels on Description. Counterpoint always supplies it, because it is the group's key.

Source: DESCR · Destination: Description

This is an optional field. The location group's readable description as maintained in NCR Counterpoint, carried across unchanged.

Counterpoint stores this as text of up to 30 characters and requires it to be populated, so a description always arrives and is never longer than 30 characters. Subscribers replacing this mapping with a formula are not held to that limit by iPaaS.com, but should keep results short enough to stay readable alongside descriptions that came straight from Counterpoint.

Source: return await ConvertLocationGroupLocationsToiPaaSLocationListAsync(Locations); · Destination: Locations

This is a recommended field. iPaaS.com accepts the group without it, but a location group with no member locations conveys nothing beyond its name, so it should be mapped for any meaningful location group sync.

Populates the group's membership. The formula walks the locations NCR Counterpoint reports as belonging to this group and, for each one, looks up the matching location already transferred into iPaaS.com. It returns the list of those iPaaS.com locations, which iPaaS.com attaches to the group.

The important behavior is what happens to a member that has not been transferred: it is left out of the list rather than causing an error, and the group transfers with the remaining members only. No message is raised against the group, so a partially populated group looks the same as a complete one. This mapping does not transfer missing locations on its own.

Subscribers or their MiSP should therefore transfer locations before location groups — the Add/Update NCR Counterpoint Location TO iPaaS.com collection handles those. Where a group has already transferred with members missing, re-running the group once its locations have landed sends the membership again with those locations resolved. Subscribers should confirm in a staging environment that the resulting membership matches Counterpoint before relying on it in production.

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.

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.