Allow the Datasource to be changed in Field Mapping

Large companies often have many copies of the same application running in different divisions or plants. For example, a company might have 1 instance of Maximo running at each of their manufacturing plants. These all need to be mapped as sources with mostly the same mapping rules.

It's possible that sometimes the mapper will choose the wrong datasource and map it completely. Then they realize they mapped the wrong source and need to change it. This is possible, but not super common.

A more common usage would be as we copy a RELEASE we then need to update the copied mappings from one source (MAXIMOA) to the new source (MAXIMOB).

By changing the Datasource we would need to cascade down the change to the Primary Table ID (GUID) to be the same table in the new datasource.

Recommendation:

1. Allow RELINTERFACESOURCE.DATASOURCE_ID to be changed to the new Datasource ID.

a. The list of new DATASOURCES should be limited to only datasources with the same APPLICATIONID and which contain the same table name referenced by the PRIMARYTABLE_ID. ie. if we are mapping MAXIMO1.ITEMS then show any other Maximo datasources that also have an ITEMS table…

2. Upon changing the datasource, update the PRIMARYTABLEID to the new table id from from the new datasourceid.
3. Update CORDATAMAP for all child records (based on INTERFACESOURCEID) to have the new DATASOURCEID, but only if the datasourceid is the same as the OLD datasource ID. Note that some mappings might be from a Different Datasource_ID so we can't just update all the mappings.
4. Update RELMAPLINAGE.DATASOURCE_ID using the same logic as for the mapping screen. Don't trigger an additional info message as these
5. If there are OTHER datasources referenced by CORDATAMAP.DATASOUCEID or RELMAPLINEAGE.DATASOURCEID - pop up an informational message to alert the user to verify all existing mappings as some secondary datasources have been used in mappings.
6. Set the MAPSTATUS to 'In-Progress' and BUILDSTATUS to 'New'