Continuous Integration (CI) is what Salesforce facilitates on its platform, which his meant to deploy loads of codes to many orgs simultaneously. Previously, these monster deployments caused a lot of traffic jam, and the deployments were not done properly or timely. Salesforce pitched in by identifying the need for an environment to do more work by introducing a set of tools to enable easier and timely CI.

The etymology of Salesforce DX is also quite interesting. Initially, it was called ‘Project Janus’. The primary logic behind the name ‘Project Janus’ was its functional resemblance with Roman God Janus, who is the god of transition. Salesforce DX was then called internally as App Cloud Developer Experience or ACDX. The App Hub was previously known as ‘Dev Lodge’ and ‘Dev Hub’ among others.

Later, this new packaging was started to be called as Salesforce Archives like the Java Archives (JARS). This further ended up in the possibility of it being called colloquially by the name SARs, which is the name of a deadly human virus, so the name ‘New Packaging’ and ‘Packaging 2’ were settled on.

Some essential Salesforce DX facts to note

# As Flosum.com points out; one can keep their old tools for the Salesforce DX too with a very few exceptions. All those tools which people are used to with Salesforce CI are available. The change sets and Sandboxes may still work in the new packaging also.

# Like many other solutions you know, Salesforce DX is never an ‘all or nothing’ type as you can even choose to use a single portion of your existing application with the latest Salesforce DX when the other portions of your app served by sandboxes or changesets.

# In fact, you have to set up an excellent project directory structure at the first point for Salesforce DX. There may be various sets of metadata which are logically connected inside a DX Projects, namely Apex Class DX Projects or Lightning DX Projects, on which you can have a customized control on who control the projects and whom all can make changes.

# You are not stuck with Salesforce DX, and you can go back at any point. If you find things are not working out as you wish on making revisions, then you can try deploying everything back into your Org and delete the repo to start it all over again. You can move back and start from scratch anytime you like to.

On Salesforce DX, you have a myriad of tools which you can integrate using the CLI. Along with it, there are also tools in the Salesforce partner ecosystem, which complements Salesforce DX like Auto Salesforce DX got unveiled in the Winter’2018, which offers a fresh and promising paradigm in Salesforce development. In this article, we are trying to discuss some of the This summary discusses some of the very interesting facts about Salesforce DX for developers and administrators.

History of Salesforce

Rabit. Along with these, Visual Studio Code too is another admirable tool to be used with Salesforce DX.

LEAVE A REPLY

Please enter your comment!
Please enter your name here