Mapping file created with gettransfermapping.py does not contain all connectors in the Mapping set

[JBomNotilyze]

When creating a mapping file from a mapping set using the gettransfermapping.py, not all connector elements are included in the resulting mapping file. A mapping set can contain various connector types:

Table
User
UserGroup
File System Paths
SAS Code Paths

But in the code, one the Table, User and UserGroup are extracted. Can this code be updated to also include the File System Paths and SAS Code Paths?

[gerrynelson63]

Hi @JBomNotilyze, there has been Viya development work on the mappings under the hood. In the tools we are currently lagging behind that work. Apologies for that. It may be some of the development work will make this tool redundant which would be ideal. If that does not happen we will update the tool. I will report back on the status soon.

[JBomNotilyze]

Thank you for the reaction, perhaps you are able to give me some advice on our case?

We are currently migrating a customer from EG to Viya4, and want to automate the importing of .egp files and the conversion to .flw files. The EGP files contain many tables and hardcoded paths, that need to be mapped to new locations on Viya4. Do you know if mapping files are the way to go, or should we write some code to adapt the .egp files before importing?

I know of the existence of the modifySASCode.exe tooling, does this tooling also work for .egp files?