This mapping collection brings the ecommerce categories maintained in NCR Counterpoint into iPaaS.com. It carries the category's display description as its name, its long-form HTML description, its place in the category hierarchy, and the display sequence number that controls the order categories are presented in.

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.

Mapping Filter

Filter Description.

The filter excludes the single category whose id is 0. NCR Counterpoint uses that id for its own uncategorized placeholder rather than for a real merchandising category, so it is held back and never reaches iPaaS.com. Every other ecommerce category transfers. Subscribers who want the uncategorized placeholder represented in iPaaS.com should review this filter before enabling the collection.

Source: DESCR · Destination: Name

This is a required field — iPaaS.com rejects the category without it. The category's display description as maintained in NCR Counterpoint, carried across unchanged and used as the category name in iPaaS.com.

Counterpoint stores this as text of up to 25 characters and permits it to be empty. That combination matters here: a category saved in Counterpoint with no description produces an empty name, and iPaaS.com rejects the record because the field is required. Subscribers or their MiSP who find categories failing to transfer should check that every category carries a description in Counterpoint, or replace this mapping with a formula that falls back to another populated value when the description is blank.

Source: HTML_DESCR · Destination: Description

This is an optional field. The long-form HTML description maintained against the category in NCR Counterpoint, carried across as-is. Categories saved without one transfer with this field empty, and the transfer succeeds either way.

The value is passed through without conversion, so whatever markup Counterpoint holds is what iPaaS.com stores. Subscribers whose destination system renders this text should confirm it handles the markup Counterpoint produces.

Source: return await GetSpaceportIdAsync(PARENT_ID, "Product Category", SpaceportSystemId); · Destination: ParentId

This is an optional field. Rebuilds the category hierarchy inside iPaaS.com. The formula takes the parent category id recorded against this category in NCR Counterpoint and looks up the matching category that has already been transferred into iPaaS.com, returning that category's iPaaS.com id.

When the parent has not been transferred yet — or the category is a top-level one with no parent in Counterpoint — the mapping resolves to empty and the category transfers as a top-level category. The transfer is not rejected.

This lookup does not pull the parent category across on its own. A child category whose parent has not yet transferred therefore lands at the top level rather than under its parent, and nothing is reported to say so. Subscribers or their MiSP who need the hierarchy intact should re-run the affected categories once the full set has transferred; the subsequent update resolves the parent and moves the category into place. Where a hierarchy is being loaded for the first time, transferring parents before their children avoids the situation entirely.

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.

At the time this documentation was written, a category whose parent has not yet transferred lands at the top level rather than under its parent, and nothing is reported to say so. The hierarchy lookup resolves the parent among the categories already in iPaaS.com; where the parent is absent — or where the category is a top-level one with no parent in Counterpoint — the value resolves to empty and the category transfers as a top-level category rather than being rejected. This lookup does not pull the parent category across on its own. Subscribers or their MiSP who need the hierarchy intact should re-run the affected categories once the full set has transferred; the subsequent update resolves the parent and moves the category into place. Where a hierarchy is being loaded for the first time, transferring parents before their children avoids the situation entirely.

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