Platform › Legacy Migration
Field Maps
How a field becomes a field. The transform is where a SAP date, a German decimal or an X-means-blocked flag is dealt with.
Where to find it
- Module: Platform
- Group: Operations
- Section: Legacy Migration
- Screen: Field Maps
Address in the console: /platform/migration-fields
List · 6 columns · 7 fields on its form · 2 of them required
What the list shows
These are the columns of the list, in the order they are drawn. Any of them can be sorted on, filtered on, hidden, or exported.
| Column | Kind | Field name |
|---|---|---|
| Source Code | Code | source_code |
| Object Code | Code | object_code |
| Source Field | Text | source_field |
| Target Field | Text | target_field |
| Transform | Status | transform |
| Required | Yes or no | required |
The form
What is asked for when a record is created here. Required fields are marked; a choice drawn from a configuration list is one an administrator can extend without a release.
| Field | Type | Choices | Notes |
|---|---|---|---|
| Object required | Choice | Looked up from existing records | |
| From | Text | ||
| To required | Text | ||
| How | Choice | copy, trim, upper, lower, date_yyyymmdd, date_iso, decimal_comma, flag_x, value_map, constant, concat, lookup, number | |
| Arguments | Text | ||
| Required | Yes or no | ||
| Note | Long text |
The rules that apply here
Everything on this screen obeys the platform rules rather than rules of its own. The ones worth knowing before you use it:
- Narrowing a list — search, conditions, sort, totals, export and saved views.
- What may be changed — the five grounds a record may not be edited on.
- Companies and business units — what the switcher above this list is doing to it.
- Creating a record — required fields, where choices come from, and how the number is allocated.
- Importing a spreadsheet — this screen accepts one, and it runs through the same rules as typing.