Manufacturers Import

The task reads manufacturers from a file and creates them in TRADElube, with descriptions per language version and with properties. It is a small one, and it usually comes before Products Import: a product refers to its manufacturer, and it cannot name one that does not exist.

What gets transferred

One manufacturer per row read: its own fields, name and description per language version, and the values of the properties you have created for the manufacturer object type.

The logo does not go along. The plan has no section for media, so you maintain a manufacturer image in TRADElube itself.

How the transfer plan is built

Four sections.

Section What sits in it
Layout The record sets: which level of the file is read, what a manufacturer is recognized by, and which rows are passed over
Common The fields of the manufacturer itself
Descriptions One record set per language version, with name and description
Properties One tab per property, created through Insert above

The Mapping assignment in the Layout section is what makes the import repeatable: its value is what the next execution finds the same manufacturer by. It is also the value the product import looks for later, where its Manufacturer row carries a field assignment. So both sides have to mean the same identifier, and where the manufacturer file carries a number and the product file the name, you settle on one of them.

A freshly created property tab is empty at first: the record set inside it is added through Insert. Without it the row has no effect.

Special features and limits

A manufacturer missing from the file stays in TRADElube. The import writes, it does not tidy up.

In the other direction this task does not exist: manufacturers come in through this channel, but not out.

Further reading