1. Contents
  2. Guides
  3. Channels and tasks
  4. Adjusting the transfer plan

Adjusting the transfer plan

On a standard channel the transfer plan is largely preconfigured, and adjusting rarely means rebuilding it. Usually it is one of four moves: activate an assignment, switch its source, set a fixed value, or write a field only under a condition. This guide shows the four moves on any task. What a transfer plan is in the first place and how it is structured is under transfer plans.

Prerequisites

  • A task with a transfer plan, of whichever channel.
  • Some patience when saving: every change to the plan leads to a complete retransfer the next time, because TRADElube cannot know which records the change affects. That is intended and harmless, but on large stocks it is a longer execution.

Step by step

  1. Read the row. Open the task and its Transfer Plan section, then the part in question. Every assignment is one row: at the front the checkbox that activates it at all, then its name, then the value with its toggles, behind it the Only on Insert and Only if filled boxes, and finally a notes field for you. As long as the checkbox is not set, the value cell stays empty. The field is then not transferred.

Assignment rows of the Common section in the product upload: checkbox, name, value with its toggles and the two condition boxes per row

  1. Activate a field or switch the source. Set the checkbox and choose the source. The pick list only shows columns whose data type fits the target field. If there is exactly one possible source, it is shown as plain text, without a list. Below the chosen source its technical designation is shown in gray. Remember that entry: it is the term you search for in the traces when you later want to check what this field transferred.

  2. Switch to a fixed value or a script. Next to the value sit toggles, and visible are exactly the kinds this assignment can be switched to: As Field Assignment, As Script Assignment and As Fixed Value. The currently active kind shows its input element instead of a toggle. A fixed value fits everything constant per channel, a currency or a customer group for instance. A script calculates, concatenates and decides, and when that pays off is under scripts in the transfer plan.

  3. Only on insert, only if filled. The two boxes behind the value are this page's gentle tools. Only on Insert writes the field only when the counterpart is first created. An entry that is maintained in the target system afterwards then stays untouched there. Only if filled keeps an empty source from overwriting the existing value.

  4. Write a field only under a condition. A condition hangs not on the individual assignment but on the record set, on its Selection assignment. If a section is to write some fields always and others only for certain rows, it therefore needs two record sets: through Insert on the section you put a second one onto the same layout node, set its Selection and tick only the fields concerned. The unfiltered record set keeps the rest.

Record set bar of a section with two record sets. The second one carries its own selection with a script

  1. Save, and read the answer. It is only saved once Save is grayed out afterwards. If the button stays active, the save was rejected, and the reason is shown as a message at the very top of the form, with the full path to the assignment concerned, while you are working further down in the plan. So scroll up before repeating the click.

Checking the result

After a plan change the next execution retransfers the whole stock. There is nothing to reset. Then check a sample: the changed value in the target system, and the transferred content in the traces, where the technical designation from step 2 appears with its value.

Frequent pitfalls

  • The asterisk behind a name means changed, not mandatory. Mapping * says, while reading in step 1, that this assignment deviates from the preset. Whether something is missing is said only by the message on saving.
  • Two tab bars on top of each other. On the product upload the outer bar selects the plan, Product versus Product Variant for instance, the inner one the section. If you follow only the inner one while reading in step 1, you configure the wrong plan, and the execution does something other than intended.
  • A column is missing from the source list. The list in step 2 is filtered by data type. The column exists, its type just does not fit the target field. The remedy is in the data format, see importing products from a file.
  • Deselecting deletes nothing. An assignment deselected in step 2 leaves in the target system whatever an earlier execution wrote. To remove a value, keep the assignment active and deliver empty deliberately, through a script for instance.

Further reading