Hello Dave!

Thank you for your post!

Make default — allows you to mark a dev hub as a default dev hub or a certain scratch organization as a default scratch organization. You can do this both globally, or just locally - for a current project.

You don't have the ability to set a regular organization as the default org to build to. However, you can try to use the standard project for deploying the sfdx project to the development organization. You can use the "Deploy to another org" feature for this.

If you have any other questions, please let me know I will be happy to help you.

Regards,

Ihor

Thank you for the quick response. So we can't use an SFDX project to work on any orgs except scratch orgs? Was there reasoning for excluding this? This is a key missing components that keeps us using VS Code instead of TWS.

Hello Dave!

Sorry for the late response!

You can use an SFDX project to work with the standard organizations. You can use the SFDX CLI panel directly from TWS. You can learn more here: https://docs.welkinsuite.com/?id=windows:how_does_it_work:sfdx_support

I hope it helps you. 

If you have any questions, please let me know I will be happy to help you!

Regards,

Ihor

Hi Ihor. Has there been any progress using Welkin Suite with SFDX and Refular orgs? The last was reponse (to use the SFX CLI) was essentially a no to TWS working with regular orgs. None of the built in functionality works. I work directly in client Sandboxes and use the SFDX project format, rendering TWS useless. It's really frustrating. I prefer TWS to VS Code, but just can't work with it at this point.