Currently, if metadata is changed from active to inactive or deleted (to delete a class or trigger) and then deployed, Welkin changes the status back to active. It would be good if Welkin could be used in place of Eclipse to delete unwanted classes and triggers.
Ability to use Welkin instead of Eclipse to delete triggers and classes.
started by
michael.summitt
20 May 2016 - 06:27 PM
2 replies to this topic
#2
kate.dulko
-
-
TWS Team
- 1721 posts
Posted 23 May 2016
Hi Michael,
Thank you for your suggestion.
Currently, the operations related to the destructive options in the meta.xml files are not implemented inside the IDE.
This is why the status for the file is changed back to the active.
Our team is going to work on it soon.
I'll keep you updated when this ability will be added to TWS.
Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com
#3
kate.dulko
-
-
TWS Team
- 1721 posts
Posted 20 Jan 2018 and edited 20 Jan 2018
Hi Michael,
I'm happy to update this topic since we have recently discussed this process in a similar topic on the forum.
So now you can use The Welkin Suite for deleting classes or triggers (from both sandboxes and production environments) according to described instructions.
Best Regards,
Kate
Kate Dulko
Customer Relations
The Welkin Suite
twitter: @KateDulko
skype id: d_katerina
e-mail: kate.dulko@welkinsuite.com