Closed amikhail0 closed 4 years ago
@amikhail0 I assume you mean an import flag, and that this would be an analogous command line flag replaceExistingMacros
. Right now, any conflicting script association definition between the current database and an attempted import will ignore the conflicting imports. Please let me know if this is what you meant. I'm currently working on adding this feature, both for the command line and the GUI import dialog.
@jmacneal That's exactly what I meant. A flag like "replaceExistingMacros" should do address this for me.
I actually get script association errors when importing conflicting script association definitions
This change will be included in our next release.
Version 2.0.23 is out and includes this new functionality.
It would be helpful if there was a command line flag to replace any imported script association configuration