Add a Mapping table in Import Action

mhemphill

The workarounds are not appropriate for my current requirement so i need to add a landing module then map it which is very costly iin terms of workspace as the data sets are very large for this client.

ask: Would like to map in bound data to a non-native version using a mapping table.

workaround: we set the import to ask each time but there are times when we wish to force the mapping to 'Current Plan' and set this in the overnight routine

Other uses: this is also useful on any dimension of the modules esp when loading external data which then has to be renamed in some way.

Creating landing modules and then remapping them leads to wasteful building