Another Salesforce blog!!!

Salesforce, Apex

March, 2018

Scratch Org Definition File

Here’s what the scratch org definition JSON file looks like: view source { “orgName”: “nisarkhan”, “adminEmail”: “myemailaddress….”, “country”: “US”, “edition”: “Enterprise”, “description”: “Work Item #12345: add picklist to widget”, “hasSampleData”: “false”, “features”: [“MultiCurrency”, “AuthorApex”], “orgPreferences”: { “enabled”: [“S1DesktopEnabled”, “ChatterEnabled”], “disabled”: [“IsNameSuffixEnabled”] } }

Salesforce DX “If you’re an ISV Partner”

If you’re an ISV building a first-generation managed package, all of your metadata is already in a single package (unless you’re using extension packages). When you deploy updates to your packaging org, you’re typically going to send everything at once. The CLI makes it easy to do this because sfdx force:source:convert operates on only one package directory […]

Salesforce DX “If you’re a Customer”

If you’re a customer with a complex, convoluted, monolithic codebase (aka the “Happy Soup”) it can be helpful to try to start breaking things up into many small, independent unmanaged packages wherever possible. Better yet, take a look at Developer Controlled Packages (DCPs) which are part of the Packaging 2 Beta in Spring ’18. Either […]

What is a Salesforce DX “Project”?

In general, a Salesforce DX Project is a new local file structure that collects your org’s metadata (code and config), org templates, sample data, and tests. The project root is often the repository root of a version control system (VCS) as well. Specifically, an SFDX Project exists when you have a local directory that contains […]