Salesforce, as everyone knows, has introduced a lot of innovative changes to the developers over the past couple of years, and everyone is on the lookout to hear about the latest from Salesforce DX.
The latest Salesforce DX keynote also seems to be very enlightening. In this article, we will discuss some commentary on the state of Salesforce DX now and in future.
The problem in Salesforce DX adoption. The major part o this issue is based on the fact that it is not an easy task to move the diverse teams into the specific source-driven development methodology.
Adding to it, DX also makes a few big requests too. The users should break up their legacy monoliths overtime to a comparatively smaller, modular structure. This is more like asking to consume only vegetables and avoid saccharine fully, which is surely good theoretically but may prove out to be so difficult in practice.
On checking the stats, we can see that only very few customers have adopted DX successfully.
So, if your team is also struggling with it, the keynote of Salesforce DX says that you are not alone. In fact, Salesforce has a plan to help, and much of these advancements are structured around the scope of providing better ways for users to adopt DX successfully.
What makes Salesforce DX adoption easier?
The primary thing which makes the adoption easier is the improvement of Metadata API and also adding support for more of Metadata types. There will be a new report on metadata API coverage which will replace the current static type Unsupported Metadata types page. The keynote address of Salesforce spokesperson also points towards the scope of supporting different metadata types in the API.
As per Flosum.com experts, it is already in the larger commitment of Salesforce to increase the Metadata API coverage step by step. For the Salesforce users, there is a scope of up-voting the favorite components in the DX through the user interface.
Even though Salesforce didn’t approve any dates, we may expect that complete Metadata API coverage will indeed be a long-term goal of Salesforce. The announcements of Salesforce spokespersons also signals that the brand is open to listening to users and working closely to address these sort of underlying issues which limits the rate of DX adoption.
The latest packaging of Salesforce DX also requires further breakups of orgs into smaller modular pieces. In order to help the development teams to accomplish it effectively, Salesforce announced their Dependency API. This tool will help developers to get a better and broader picture of how metadata may interact with itself. This new API makes it easier for the developer to run queries to retrieve info about dependencies of metadata.
Dependency API is another command-line tool, which is expected to be available by late 2018. This tool is expected to a great move in enhancing the adoption of Salesforce DX and also making it much simpler to the developers to restructure the org in terms of source-driven application development.
As we always found, Salesforce DX has the fame of delivering features quicker based on the user requirements. They are always focused on the quality of releases and also to keep the developers optimally productive.