Skip to main content

iPaaS.com to NCR Counterpoint Message Mapping Documentation

Field-level mapping documentation for the NCR Counterpoint Message collections.

Summary

This mapping collection sends iPaaS.com messages to NCR Counterpoint, where they arrive as internal Counterpoint messages for store staff to read. It lets a notice raised in iPaaS.com, or passed into iPaaS.com by another integration, reach the people working in Counterpoint without anyone signing in to iPaaS.com. Each message becomes a Counterpoint message with the iPaaS.com message text as its subject and the message details as its body, sent from the Counterpoint user the collection names, to the Counterpoint users it names.

ID Format

  • Manual Sync id: the iPaaS.com message id, for example 4490347. This collection writes outbound from iPaaS.com, so the id entered on the Manual Sync page is the iPaaS.com-side id of the message, not a Counterpoint value.

  • External ID saved after transfer: once a message has been sent, iPaaS.com records the Counterpoint message id it was given as the external ID on a dedicated platform-managed external-ID record, for example 100000000000101. Counterpoint numbers the message itself; nothing in the mapping sets the id.

Deleted Record Support

This collection does not carry deletions. A message removed in iPaaS.com is kept in Counterpoint. See NCR Counterpoint Known Limitations.

Mapping Collection Status

  • Status: Enabled. No mapping filter is applied.

  • Trigger Events: the iPaaS.com message/created trigger, enabled in the subscription configuration's Outbound Data Flows section. Sending messages to Counterpoint does not need the optional Messages feature in the Counterpoint database.

Duplicate or Conflicting Records

This collection has no Collision Handling Method. It adds messages only: each iPaaS.com message sent to Counterpoint becomes a new Counterpoint message, numbered by Counterpoint, and is linked to it by its external ID. A later change to a message that has already been sent is not carried to Counterpoint (see Additional Notes).

System Caveats

NCR Counterpoint Caveats

  • The subject is limited to 50 characters: Counterpoint stores a message subject as text of up to 50 characters and refuses a longer one. The shipped SUBJ formula therefore sends the first 50 characters of the message text. The full text is still carried in the body, which has no length limit.

  • One recipient record per user: Counterpoint records a separate recipient entry for each user listed in SENT_TO, so a message sent to MGR,Z appears in the message inbox of both users. Each user id is up to 10 characters.

  • Users must exist in Counterpoint: SENDER_ID and every user in SENT_TO should be user ids configured in the Counterpoint installation. Subscribers or their MiSP should confirm the ids before enabling this collection.

iPaaS.com Caveats

  • Severity and type are not sent: a Counterpoint message is sent with normal importance and is not shown as a popup. The iPaaS.com severity and type are not mapped to Counterpoint.

Integration Flow

  1. No records are transferred as prerequisites for this collection.

  2. The message is read from iPaaS.com by its message id, either from the message/created trigger or from the id entered on the Manual Sync page.

  3. The message is added in Counterpoint, which numbers it and records one recipient entry per user in SENT_TO. The Counterpoint message id is recorded as the external ID.

Mappings

Add NCR Counterpoint Message FROM iPaaS.com

Mapping Type

Source Field (iPaaS.com)

Destination Field (NCR Counterpoint)

Description

Static

"Z"

SENDER_ID

Required. The Counterpoint user the message comes from. Placeholder value — replace during implementation.

Dynamic Formula

Formula

SUBJ

Recommended. The message text, shortened to 50 characters.

Field

Details

MSG

Recommended. The message details, in full.

Static

"MGR"

SENT_TO

Required. The Counterpoint user or users the message is sent to. Placeholder value — replace during implementation.

SENDER_ID — Static

Source: "Z" · Destination: SENDER_ID

This is a required field. Counterpoint refuses a message without a sender. The Counterpoint user the message appears to come from, a user id of up to 10 characters. Choose a user that store staff will recognize as the source of integration messages.

Placeholder value — replace during implementation: "Z" is an example Counterpoint user id, not a Counterpoint default. Replace it with a user id from your own Counterpoint installation before enabling this collection, and confirm the user exists in Counterpoint.

SUBJ — Dynamic Formula

Destination: SUBJ

if (string.IsNullOrEmpty(Text))
    return Text;
return Text.Length > 50 ? Text.Substring(0, 50) : Text;

This is a recommended field. The iPaaS.com message text becomes the Counterpoint subject. Counterpoint stores a subject as text of up to 50 characters and refuses a longer one, so the formula sends the first 50 characters of a longer text; for example, a 70-character text arrives as its first 50 characters. The message details, mapped to MSG, carry the full content, so nothing is lost from the message.

MSG — Field

Source: Details · Destination: MSG

This is a recommended field. The iPaaS.com message details, carried across in full as the body of the Counterpoint message. Counterpoint keeps the body as plain text with no length limit.

SENT_TO — Static

Source: "MGR" · Destination: SENT_TO

This is a required field. Counterpoint refuses a message without recipients. The Counterpoint users the message is sent to: a single user id, such as MGR, or several separated by commas, such as MGR,Z. Counterpoint records a separate recipient entry for each user listed, so every one of them finds the message in their Counterpoint inbox. Each user id is up to 10 characters.

Placeholder value — replace during implementation: "MGR" is an example Counterpoint user id, not a Counterpoint default. Replace it with the user id, or the comma-separated user ids, of the people in your own Counterpoint installation who should receive integration messages, and confirm each user exists in Counterpoint.

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 requeued and retried automatically, but each retry fails the same way until the cause is corrected. Correct the cause, then transfer the record again through Manual Sync rather than waiting for the next retry.

Testing & Validation

  1. Replace the placeholder sender and recipient with user ids from the target Counterpoint installation, and confirm each exists in Counterpoint.

  2. Create a message in iPaaS.com, send it through Manual Sync by its iPaaS.com message id, and confirm it appears in each recipient's Counterpoint inbox with its subject and body.

  3. Send a message whose text is longer than 50 characters and confirm it arrives with the first 50 characters as its subject and the full details as its body.

  4. Enable message/created in Outbound Data Flows and confirm a newly created iPaaS.com message reaches Counterpoint on its own.

Additional Notes

  • Updating or deleting messages is out of scope: this collection adds messages. A change to an iPaaS.com message after it has been sent, or its removal, does not change or remove the Counterpoint message.

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


Related Documents

Did this answer your question?