Skip to content

6.1 – Map Transform

Adding Fields to the Dataset

An Aggregate transform can create records, but it cannot add fields. Every field the shipment charge records need must exist on the dataset before the Aggregate runs. The Map transform adds them.

Step 7 maps the four fields you create here into the Sage 300 order: one on the order header and three on the order lines.

Transform > Field Mapping

  1. Double-click the Map transform to re-open it, then press the Field Mapping tab.

  2. Check that Orders is selected in the Current Transaction Id drop-down above the grid.

    The Map transform's Field Mapping tab, with Orders selected in the Current Transaction Id drop-down and the Add, Edit and Delete buttons above the field grid

  3. Press Add and create the field that will carry the Sage 300 order number:

    1. New Field Name
      • Sage300OrderNumber
    2. Type
      • Text
    3. Evaluate
      • Unticked
    4. Evaluate String
      • Leave blank

    The Field Mapping dialog for Sage300OrderNumber, with Type set to Text, Evaluate unticked and an empty Evaluate String

    Leave the value empty. Step 7 maps this field to the Sage 300 Order Number, which Sage 300 generates during the import. The field goes in empty and comes back with the order number.

  4. Press the tick to save the field. IMan adds it to the end of the Orders list.

    The end of the Orders field list, with Sage300OrderNumber added below TaxGroup

The order line fields

The miscellaneous charge lines that 6.2 creates are order detail records. The fields they need belong to the OrderDetails transaction, not to Orders.

  1. Change the Current Transaction Id to OrderDetails.

  2. Press Add for each of the following three fields:

    New Field Name Type Evaluate Evaluate String
    LineType Integer ✘ 1
    ExtendedPrice Decimal ✘ leave blank
    MiscChargeId Text ✘ leave blank

    The Field Mapping dialog for LineType, with Type set to Integer, Evaluate unticked and a static Evaluate String of 1

    • Set Type carefully here. It did not matter for the customer fields in step 4. LineType is a whole number, ExtendedPrice is a money amount, and Sage 300 rejects a value it cannot convert.
    • LineType is the Sage 300 order line type: 1 for an item line, 2 for a miscellaneous charge. Every line read from the workbook is an item, so the static value is 1. The charge records created in 6.2 set theirs to 2.
    • Leave ExtendedPrice and MiscChargeId empty. Only the charge records carry a value in them, and 6.3 uses the empty value to filter out the charges that do not apply.

  3. With all three added, the OrderDetails list ends with the new fields, their types and LineType's static value.

    The OrderDetails field list showing LineType, ExtendedPrice and MiscChargeId added after UnitPrice, with their types and LineType's Evaluate String of 1

  4. Press Refresh.

  5. Press Close at the bottom of the transform, then Save the integration.

A transform pane has no Save of its own

A transform pane has no Save of its own. Close commits the transform to the integration held in the designer. Save then writes the integration to the server. If you close the transform and do not save the integration, you lose the work.

Step 6.2: Aggregate >