Is there a way to prevent an Appian object in conflict to be overwritten while importing the package. If there is no way to prevent a particular conflict to be overwritten . Is there any properties file settings to prevent overwriting of all conflicts in that import?
what I am looking for is something like importSetting.FORCE_UPDATE=true in import customization properties file, ideally for one particular object in conflict or all objects if that's not possible
Discussion posts and replies are publicly visible
What is the use case here? If you would keep the old object on the target environment, your application might break because it relies on the new version.
don't put the element you try not to overwrite into the package you are exporting. Just transport the ones you like to update. Should be the easiest way.But I think, its in general not possible in the way you address it here.
This would be my overall suggestion. That or resolve the conflict first - depending of course on what the conflict is and why it's there.
Agree. If you do not want to update the object in the target environment, do not include it in your deployment package. This is my best practice as well.
If you have one application in an environment that relies on a different configuration for this object than an application in another environment, I assume this would be on the agenda to resolve.
© 2022 Appian. All rights reserved.