This mapping collection brings NCR Counterpoint users into iPaaS.com as employees. A user iPaaS.com does not yet hold is added; a user it already holds is updated. It carries the user's name, split into its given and family parts, and an e-mail address for them.

This family does not itself carry deletions. Where a separate Delete collection exists for this entity it handles removals from Counterpoint to iPaaS.com; otherwise a removal in Counterpoint is not propagated. See NCR Counterpoint Known Limitations.

Source:

Destination: FirstName

This is a conditionally required field. iPaaS.com requires that at least one of FirstName or LastName is supplied, and rejects the employee if both are missing. NCR Counterpoint holds a user's name as a single combined value rather than as separate given and family names, so this mapping splits it. The formula looks for a space in the combined name. If it finds one, it returns everything before the last space. If the name contains no space at all, it returns the whole name unchanged.

Because NCR Counterpoint always populates the user name, this mapping always produces a value, and it is what satisfies the requirement that at least one name field is present. A single-word name therefore transfers as a first name with no last name, which iPaaS.com accepts.

Splitting on the last space is a starting point, not a parsing rule that fits every name. A user recorded as "Mary Anne Smith" transfers as first name "Mary Anne" and last name "Smith"; a user recorded as "Juan Carlos de la Cruz" transfers as first name "Juan Carlos de la" and last name "Cruz". Subscribers or their MiSP whose Counterpoint users follow a different naming convention should adjust this formula and the LastName formula together, so that the two stay consistent with each other.

NCR Counterpoint stores the combined name as text of up to 40 characters and always supplies it. Subscribers replacing this mapping with a different formula are not held to that length by iPaaS.com.

Source:

Destination: LastName

This is a conditionally required field. iPaaS.com requires that at least one of FirstName or LastName is supplied. This mapping is the second half of the name split described under FirstName, and it is not independently required, because FirstName always produces a value.

The formula looks for a space in the combined NCR Counterpoint user name. If it finds one, it returns everything after the last space. If the name contains no space, it returns an empty value, and the employee transfers with a first name only.

Subscribers or their MiSP changing this formula should change the FirstName formula in the same collection at the same time. The two divide one Counterpoint value between them, and editing only one of them either duplicates part of the name across both fields or drops part of it entirely.

Source: if ( IsEmpty(EMAIL_ADRS_1)) { return NAM;} else { return EMAIL_ADRS_1;} · Destination: EmailAddress

This is a required field — iPaaS.com rejects the employee without it, and will not accept a null or empty value. This is the difference this mapping exists to bridge: iPaaS.com requires an email address on every employee, and NCR Counterpoint does not require one on a user.

The formula reads the user's first email address. When NCR Counterpoint holds one, it is passed through unchanged. When the user has no email address recorded, the formula falls back to the user's combined name so that the required field is populated and the transfer succeeds.

Subscribers and their MiSP should understand what that fallback means in practice. A user with no email address in NCR Counterpoint arrives in iPaaS.com with a name where an email address is expected. The transfer succeeds, but the resulting value is not a working address and is not suitable for sending mail to. iPaaS.com also expects employee email addresses to distinguish one employee from another, so two Counterpoint users who both lack an email address and happen to share the same name produce the same value here.

The fallback is deliberate — it is what allows users to transfer at all from a system that does not require the field. Subscribers who want genuine addresses on their iPaaS.com employees should populate the email address against the user in NCR Counterpoint before the transfer runs, rather than relying on the fallback. Subscribers who would rather a user without an email address not transfer at all can add a collection filter to exclude them.

NCR Counterpoint stores the email address as text of up to 50 characters and permits it to be empty.

Parent: Add/Update NCR Counterpoint User TO iPaaS.com.

Source: Parent.NAM · Destination: Name

This is an optional field. The name recorded against the address, which iPaaS.com uses to label the address rather than to identify the employee.

NCR Counterpoint does not keep addresses as separate records the way iPaaS.com does. The address fields live directly on the user record itself, so every mapping in this collection reads from the parent user rather than from an address record of its own. That is why each formula in this collection is prefixed with Parent — there is no separate address row in Counterpoint to read from. It also means this collection only produces an address as part of a transfer of the user that owns it; it does not run independently.

Because Counterpoint has no distinct name for the address, this mapping reuses the user's own combined name. NCR Counterpoint stores that name as text of up to 40 characters and always supplies it, so this field always arrives populated.

Source: Parent.ADRS_1 · Destination: Address1

This is an optional field. The first line of the user's address as recorded in NCR Counterpoint, carried across unchanged. NCR Counterpoint stores this as text of up to 40 characters and permits it to be empty. Where the user has no address line recorded, the field transfers empty and the employee address is still created.

Source: Parent.ADRS_2 · Destination: Address2

This is an optional field. The second line of the user's address as recorded in NCR Counterpoint, carried across unchanged. NCR Counterpoint stores this as text of up to 40 characters and permits it to be empty. Most user records leave it empty, and that is not an error.

Source: Parent.ADRS_3 · Destination: Address3

This is an optional field. The third line of the user's address as recorded in NCR Counterpoint, carried across unchanged. NCR Counterpoint stores this as text of up to 40 characters and permits it to be empty. Most user records leave it empty, and that is not an error.

Source: Parent.CITY · Destination: City

This is an optional field. The city recorded against the user in NCR Counterpoint, carried across unchanged. NCR Counterpoint stores this as text of up to 20 characters and permits it to be empty.

Source: Parent.CNTRY · Destination: Country

This is an optional field. The country recorded against the user in NCR Counterpoint, carried across unchanged. iPaaS.com does not constrain this field to a fixed list of country names or codes on employee addresses, so whatever NCR Counterpoint holds is what arrives — the value is not normalized in transit. Subscribers whose Counterpoint users record country inconsistently, or who need a specific format such as a two-letter code, should replace this mapping with a Lookup Translation or a formula that produces the form they need. NCR Counterpoint stores this as text of up to 20 characters and permits it to be empty.

Source: Parent.STATE · Destination: Region

This is an optional field. The state or province recorded against the user in NCR Counterpoint. iPaaS.com calls this Region because it accommodates states, provinces, and other sub-national divisions; NCR Counterpoint records it as a state. The value is carried across unchanged and is not normalized in transit. NCR Counterpoint stores this as text of up to 10 characters and permits it to be empty.

Source: Parent.ZIP_COD · Destination: PostalCode

This is an optional field. The postal or ZIP code recorded against the user in NCR Counterpoint, carried across unchanged. NCR Counterpoint stores this as text of up to 15 characters and permits it to be empty, and it accepts both five-digit and extended ZIP formats as well as non-US postal codes. Whatever is held is what transfers.

The formula for this mapping begins with a leading tab character before the value it reads. The tab is insignificant to how the formula evaluates — the mapping resolves to the parent user's postal code exactly as if the tab were not there — and it does not need to be removed for the mapping to work correctly.

Source: Parent.PHONE_1 · Destination: PhoneNumber

This is an optional field. The first phone number recorded against the user in NCR Counterpoint, carried across unchanged. iPaaS.com does not impose a format on employee address phone numbers, so the value arrives in whatever form Counterpoint holds it, including any punctuation or extension text. Subscribers who need a consistent format across systems should replace this mapping with a formula that produces it.

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.

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