5

I'm diving in head first into Salesforce DX. Spinning up scratch orgs, using the packaging 2 API, and converting between Metadata API and Salesforce DX friendly formats is making my eye twitch, but I digress...

I believe I understand the basics. Create source locally (in my case, via VS Code with SFDX extensions), push to scratch org, test/verify, etc. I can see creating Apex (classes, triggers) and other text-based components locally, but what about visual components (like Flow, Workflow, etc.) and fields? Do I have to define the XML in VS Code? Or, is there a way to create them, quickly/easily pull them down to my source?

What is the (recommended|preferred|best practice) way of creating non-text-based components using Salesforce DX?

4

DX is actually intended to have development performed primarily in the scratch org. As an example, you'd create the Flow in your scratch org, then use force:src:pull to get the new metadata into your source. Scratch orgs have additional tables to support this feature; when metadata is modified in the org, it's marked as dirty so that DX knows which files to update in your repo.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.