Reference manual

Transfer fields window

The transfer fields mapping is available from code in Object view and Extended view when TransferFields has two different tables for source and target. Invoke by using the context menu on TransferFields.

Alternatively, this window can be opened via the object context menu (enabled for tables, only).

Use this window to see how fields are mapped. The mapping includes fields from all extensions that are part of the workspace. The mapping is sorted by field number, as this what the mapping is based on (not the field name).

The following is a mapping of TransferFields(TimeSheetDetail) in table 5510 "Employee Time Reg Buffer":

Prism for AL: Transfer fields mapping
Transfer fields mapping.
# Name Description
1 Source object The source table for the mapping, i.e. where values are copied from. This is the argument to TransferFields, here Time Sheet Detail.
2 Target object The target table for the mapping, i.e. where values are copied to. This is the record on which TransferFields is called, here Employee Time Reg Buffer.
3 Direction The direction of the TransferFields (from source on the right to target on the left) corresponding to target.TransferFields(source).
4 Search Enter a search string to filter fields by name.
5 Change direction Swaps source and target tables.
6 Field number The field number of a field in the source and/or target tables.
7 Target name Name of field with the row's field number in the target table. This is left blank if the source table does not have any fields with that number.
8 Target type The type of the field in the target table. This is left blank if the target table does not have any fields with that number.
9 Source type The type of the field in the source table. This is left blank if the source table does not have any fields with that number.
10 Source name Name of field with the row's field number in the source table. This is left blank if the source table does not have any fields with that number.
11 Mapping indicator

Indicates whether the field is mapped or not with additional information added by different icons and tooltip.

Not mapped: The field is not mapped (either source or target does not have this field number).

Mapped ok: The field is mapped (both source and target have this field number).

  • Exact match: The types match exactly.
  • Dimension fits: The source dimension is less than the target dimension.
  • Enum coersion: Enum fields are considered the same data type even on different enum types.

Mapped error: The field is mapped and the types of the source and target fields differ which can lead to issues. These are the cases:

  • Type mismatch: The types do not match.
  • Text overflow: The source dimension is greater than the target dimension.
  • Type mismatch in different apps: Matching fields of different extensions are ignored when types do not match.