Table of Contents
Secondary One-to-Many database tables are bound to Table Named Ranges (TNR). In subsequent transactions, it is possible that the size of the table named range is modified: either new columns have been added, old columns are removed, or the relative positioning of columns may have changed.
In these scenarios, you must consolidate any One-to-Many tables that are bound to those named ranges in order to ensure that the mapping for the database is consistent with the changes that were made to the underlying Table Named Range (TNR).
This screen allows you to resolve this scenario by performing a mapping between the columns that are in the Table Named Range versus the columns that currently exist in the database table.
Named Range Column
The Named Range column on the screen provides you with information regarding the columns in the existing Table Named Range (i.e. based on the latest iteration of the workbook). If there are headers, then the header information is displayed and some sample cell values are shown in order to give you a general idea of which column this is referring to.
The Database Column column on the screen provides you with a list of columns that currently exist in the target One-to-Many database table.
If the column is a new column that did not exist in the previous version of the workbook's Table Named Range, then you can select the <Add New> option to create a new database column corresponding to the target named range column. Otherwise, existing Table Named Range columns can be mapped to existing database columns from the One-to-Many table.
After your mapping is completed, you can click on the Update Mappings button to save the new mapping information. Any new columns will be created automatically using the information retrieved from the table named range metadata. These columns can then subsequently be edited using the Edit Column button on the Edit Table page.
If an existing table column is not mapped to a column from the table named range, then it will be deactivated.