Salesforce DX, used primarily by developers, allows users to have true version control. Version control allows developers to have better control over collaboration, auditing, and disaster control. It is also an important part of an agile release plan. It also helps users build and release new features quickly and with minimal risks.
-Quick Roll back -Easily backup of the org -With the help of scratch developers do their work without any interference. - Concept of Version control of release.
Improved Version Control System (VCS) synchronization through change-tracking of setup features, allowing developers to have better control over collaboration, auditing, and disaster control
The ability to improve quality and time to market through Continuous Integration (CI) and Continuous Delivery (CD)
More fine-grained visibility and clarity into the change management of the Production Org
The ability to implement more agile release management processes
Using Salesforce DX to Export and Import records into regular Salesforce Instances without dependency on developer hub org In today’s continuous integration solution built for Salesforce, if you need to load sample data into Salesforce then either we use command line dataloader or custom tool built to import export records. With Salesforce DX, we can import and export records right from Salesforce DX. Again, if you are new to Salesforce DX, then first read this blog post to quickly understand what is Salesforce DX. We don’t need Developer Hub or Scratch Orgs to use Salesforce DX for import and export. In this blog post, I have used my regular developer org for demo. First step as always, to make sure if Salesforce DX CLI is connected to your Org or not ? If its not connected then use below command to connect and give alias which is easy to remember.
I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too. Thanks, Ajay Dubedi
Salesforce DX, used primarily by developers, allows users to have true version control. Version control allows developers to have better control over collaboration, auditing, and disaster control. It is also an important part of an agile release plan. It also helps users build and release new features quickly and with minimal risks.
-Quick Roll back
-Easily backup of the org
-With the help of scratch developers do their work without any interference.
- Concept of Version control of release.
Refer this links
https://developer.salesforce.com/blogs/2018/02/getting-started-salesforce-dx-part-1-5.html
https://bluecanvas.io/blog/2017-11-27-how-to-use-salesforce-dx
https://wilsonmar.github.io/salesforce-dx/
https://www.jitendrazaa.com/blog/salesforce/getting-started-with-salesforce-dx-salesforce-developer-experience/
https://blog.texei.com/our-move-to-salesforce-dx-and-developer-controlled-packages-7470c08cbc5c
https://www.galaxe.com/resources/blog/the-pros-and-cons-of-using-salesforce-dx/
Using Salesforce DX to Export and Import records into regular Salesforce Instances without dependency on developer hub org
In today’s continuous integration solution built for Salesforce, if you need to load sample data into Salesforce then either
we use command line dataloader or custom tool built to import export records. With Salesforce DX, we can import and export
records right from Salesforce DX. Again, if you are new to Salesforce DX, then first read this blog post to quickly understand what is Salesforce DX.
We don’t need Developer Hub or Scratch Orgs to use Salesforce DX for import and export. In this blog post, I have used my regular developer org for demo.
First step as always, to make sure if Salesforce DX CLI is connected to your Org or not ? If its not connected then use below command to connect and give alias which is easy to remember.
I hope you find the above solution helpful. If it does, please mark as Best Answer to help others too.
Thanks,
Ajay Dubedi