The Mapping screen in the TO DB process allows users to control which columns are exported to the target database and how they appear. This configuration is essential for aligning your output with the structure, naming conventions, and requirements of the destination database table.
With this screen, you can:
- Select only relevant columns from the input source
- Rename columns to match the schema of the external database
- Define the column mapping for clear data transfer
Only the columns listed on this screen will be included in the export. If a column is not added to the list, it will not be written to the target database—even if it exists in the input data.
By using this screen effectively, you ensure your data is clean, relevant, and properly structured for the destination. It also helps prevent schema mismatches and makes downstream integration seamless.
The Mapping screen includes a user-friendly interface with several tools to manage your columns efficiently. Let’s explore each feature in detail.
Add
This option allows you to manually add specific columns from the input source. You can use this when you want to export only a few selected fields.
Add All
Clicking Add All will automatically populate the mapping list with all columns available in the input source. This is useful if you want to export the complete dataset without having to add each column one by one.
Clear
This option removes all mapped columns from the list. It’s helpful when you want to start over or completely change your export structure.
Import
The Import feature allows you to upload a list of columns from an Excel file. This is ideal when you already have a predefined column list or format specification prepared externally.
Export
With this option, you can export the currently mapped columns to an Excel file. This is helpful for documentation, versioning, or sharing the mapping setup with others.
Understanding the Column Fields:
The table on the Mapping screen includes four key fields for each mapped column:
Order
This field defines the sequence in which columns will be written to the target database table. By assigning an order number to each column, you can control their position during the export—columns with lower numbers are placed earlier in the table structure.
While column order typically doesn't affect how databases store data, maintaining a consistent order can be helpful for readability, querying, and integration with downstream systems that may expect columns in a specific sequence.
Please note that the Column ordering is purely for structural organization and does not impact the data content or schema enforcement by the database.
Name
This is the display name of the column that will be exported to the target database. You can use this field to rename columns from the input source to match the naming conventions or schema requirements of the destination table.
Renaming is especially useful when your internal column names are technical or system-generated, and the external database expects more business-friendly or standardized names. For example, you may rename 'city' to 'Town'.
Source
This field specifies the original column name from the input source. It defines which actual data column is being used for the mapped output. The Name is just a label, while Source is the actual reference.
Note
This optional field lets you add comments or context for each column. You can use this to document business logic, mapping rationale, or any special handling the column requires.
Delete Column
You can also remove a specific column from the list by clicking the delete icon located at the end of the row, just after the Note column.