Hi Laszlo,

Thank you for contacting us on this.

This is the known issue to us, and we are going to work on this during one of the nearest sprints.

The issue applies to a regular deploy using the 'Deploy' functionality inside a project related to a production organization.

Currently, as a workaround, you can use the 'Deploy to Organization' functionality - it is available for you in the menu Deploy. In this case, you can make a deployment to the same org - please select the 'Use organization from the project' option at the first stage of this deployment process and proceed with all further steps as usual.

Also, you haven't been faced with this issue before, when you deployed from sandbox to your prod, since during the deployment to your prod using the 'Deploy to Organization' the IDE runs tests as this is required.

Hope this would help and soon we will solve the issue when a regular deployment from a project to a related production organization fails.

Best Regards,

Kate

Is there any progress on this?  I am currently evaluating the product and bumped into this right away... I don't necessarily want to use the deploy to organization as that looks like it will deploy the entire project, not just a single object

I've reproduced the issue. And used the 'Report a bug" feature of TWS. 

Thank you.

avi, on 04 Sep 2018 - 07:37 PM, said:

Is there any progress on this?  I am currently evaluating the product and bumped into this right away... I don't necessarily want to use the deploy to organization as that looks like it will deploy the entire project, not just a single object

 Hey avi, I use TWS for a lng time now. I can confirm, that "deploy to organization" does not deploy your entire project. Only your selected items. Like a change set. But without the waiting.

Hi All,

Thank you for your question.

Right now I cannot tell you when exactly this will be done, however, we will work on this during the nearest months.

I will keep you updated on the process of the implementation of this feature.

If you would have any other suggestions, please let us know - we'll be happy to assist.

Regards,

Ihor

Using the Deploy to Organization option is fine if you are deploying items that require the running of Apex Tests.  I have a scenario where I am only deploying email templates.  In a normal Changeset the "default" option would deploy without running apex tests.  I didn't see that opton to use the Default so now I have to run Apex tests for items that normally wouldn't need them using a standard changeset.

Hi Robert,

Thank you for letting us know about your use case - this information is helpful for us. This feature is still in our roadmap for the nearest future and we are going to implement it in a month or two if nothing won't change.

Regards,

Ihor

Hi guys,

I hope you are doing well.

I'm going to close the current topic since the required functionality was implemented in the Bloom R29 (for Windows) and Blaze R22 (for Mac) version of The Welkin Suite IDE.

If you have any questions, please let us know - we'll be happy to answer them and provide you with all the information.

Have a nice day!

Regards,

Ihor