cancel
Showing results for 
Search instead for 
Did you mean: 
ChristopherJank
Level 7
Status: Not Planned

I can at the moment just say i dont want import if the object is still existing, this is not for new objects possible
2 Comments

Hello @Christopher Janke

Thanks for taking the time to raise your idea.

The functionality you describe is part of the "Import Conflict" feature that exists to resolve conflicts when importing releases into the system that contain items that already exist in the target environment, which is why it doesn't show up for "new" items.

If you don't want to import a particular process or object, can I ask why you don't just exclude the item from the release package?

I'm going to mark this idea as Needs More Info pending your response.

Regards,

Rob

Status changed to: Not Planned

Hi @ChristopherJank,

 

I'm going to mark this as Not Planned due to lack of additional information - at the moment to achieve the outcome that you describe it is necessary to remove the unwanted processes/objects from the release package to prevent them from being imported as "new" items in the target environment.

 

Regards,

Rob