Categories Update
The action brings a category from the ERP system into TRADElube. Where it does not exist here yet, it is created. Where it does, it is changed. It is the route for everyone who maintains their category tree in CAO-Faktura and wants to pass it on from there into the connected shops.
What gets transferred
Each call is about exactly one category. The ERP system names its identifier, and TRADElube looks up the matching channel mapping by it. Where none is found, TRADElube creates a category and remembers the identifier for next time.
Where the category ends up in the tree is decided by the identifier of the parent category sent along. Where none comes along, or the one named is unknown here, TRADElube hangs the category below the Root Category from the channel's configuration.
An image does not come along, and cannot be supplied later either. TRADElube keeps no image on a category. The detail view has no field for it. In full under Categories Image Upload.
How the transfer plan is built
The plan sits in the channel, in the Transfer Plans section under Categories and there in the Update tab. It has two sections.
| Section | What sits in it |
|---|---|
| Common | The single assignment Parent Category, so the place in the tree |
| Descriptions | The texts: Name, Short Description, Description and the three meta fields |
Every row in the Descriptions section offers two sources to choose from, the ERP system's single-language field and its multilingual counterpart. You enter the multilingual one where your ERP system keeps its texts per language. Otherwise the other one is enough.
Where your client keeps several language versions, the section gets a tab of its own per language version. With exactly one, the tab bar is absent and the assignments sit directly below the section.
Special features and limits
Which language version a delivered text lands in is decided by the Languages tab in the channel's Mappings section. It holds your client's language per language identifier of the ERP system. A language version without a counterpart stays untouched.
The Root Category itself cannot be changed. A call hitting it is answered with an error and carried in traces as Failed. It is the bracket around the whole subtree, and an ERP system renaming or re-hanging it would shift everything below.
The tree is built in the order the ERP system sends it. A category whose parent has not arrived yet lands below the Root Category at first and moves to its place as soon as the parent follows.
Further reading
- CAO-Faktura: login details, configuration, mappings and the other eighteen actions
- Categories Export: the other way round, out of TRADElube into the ERP system
- Categories Erase: what happens when the category disappears in the ERP system
- Categories (reference): the category tree in the client and how you maintain it
- Transfer plan (concepts): plan, section and assignment, plus the three ways to determine a value