Ability to rename a version without breaking the import mapping

Ability to rename a version without breaking the import mapping

When performing a module to module import from the same model, if a version which is used as the source of an import is renamed, both the old and new version names will be listed as source items. The import will display a successful import message, but the number of rows Updated/Ignored/Failed will be empty and the module data will NOT be updated to reflect any data changes from the source module. This is only an issue when you have Map items manually selected. The system is able to handle the version rename when Match on names or codes is selected.

1 Comment
Community Manager
 
Status changed to: Considered for Future Roadmap
Users Online
Currently online: 188 members 527 guests
Please welcome our newest community members: