Hi Marin,

Thank you for sharing this information with us and for bringing this to our attention.

We understand that the case when the IDE has rewritten your changes is really frustrating and when you got not appropriate error also causes inconvenience to a working process. Thanks to your post we have found what changes should be done to improve the build functionality in TWS and avoid this and similar issues.

To be more detailed: a reason for this issue is that the IDE doesn't handle properly the temporarily lock of an organization's administration setup. In this case, TWS didn't recognize this response as an error and this is why the build process finished successfully. However, as the IDE detected that the file is different on the organization and in your TWS project, it has reloaded this file from the org.

We have added the work on this issue to our current sprint and we will release the necessary changes to handle this response from Salesforce already in the next version of The Welkin Suite IDE.

Thank you one more time for contacting us with this issue. If you would have any other questions or suggestions, please contact us. we would be happy to assist.

Regards,

Kate

Thanks Kate. Paying you is money well spent for welkinsuite - this is exactly what i'd expect to hear from customer service.

Hi Marin,

You are more than welcome, and it is great to hear that our support team is living up to the expectations of our users.

Regards,

Kate

Hi Martin,

I hope you are doing well.

I'm happy to let you know that today we have released a new version of The Welkin Suite for Windows - Bloom R16. This version contains the necessary changes so that the IDE handle a temporarily lock of organization's administration setup and provide you with an appropriate information in this case when you are building your changes to Salesforce.

If you would have any additional questions or suggestions - please let us know. We'll be happy to assist.

Regards,

Kate