data-assistant
data-assistant copied to clipboard
Esri
Data, TargetFields and Source Fields in xml, is there a reason
What is the purpose of storing them in the xml. Can they be removed and just use the source to target field mapping? They can pull from the layer to ensure any new fields are present. This would help us as we are trying to construct the xml files from another process
@SteveGrise @pLeBlanc93
The list of source and target fields is used by the field mapping tool to present the list of source and target datasets. There should be no problem for other tools if they are not present in your mapping files. @MikeMillerGIS @pLeBlanc93
My only concern is what happens if I generate the file and then add a Field to the target layer, how do I get that into the file? I rather not recreate as I have some really big field maps.
Should there be a refresh file in DA?
@pLeBlanc93 do we need to do this on our end, merge an existing XML da file with the translation map to pick up missing fields? My concern doing it from DA, is the DA does not know what fields to not add, I.e. UN fields and fields for other AG/AT.
We could add a field sync, there are a few tricky cases but it's possible. Have you tried using the 'match library' functionally? You might find that to be useful. Let's discuss...
On 20 Jan 2017 4:27 a.m., "Michael Miller" [email protected] wrote:
My only concern is what happens if I generate the file and then add a Field to the target layer, how do I get that into the file? I rather not recreate as I have some really big field maps.
Should there be a refresh file in DA?
@pLeBlanc93 do we need to do this on our end, merge an existing XML da file with the translation map to pick up missing fields? My concern doing it from DA, is the DA does not know what fields to not add, I.e. UN fields and fields for other AG/AT.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Esri/data-assistant/issues/98#issuecomment-274036848, or mute the thread https://github.com/notifications/unsubscribe-auth/AEh3BE_60MBKgwYPU3WDuYgO5HuLeITyks5rUIwWgaJpZM4LomLB .
@SteveGrise Added this to v3 and wanted to look at removing the source and field definitions from the config file and just read them into memory from the layer when the file it loaded
Maybe we can use a refresh button on the data mapping which could reload the fields and compare any changes, add any new and prompt the user for conflicts.