DX Complete Guide - Package-Based Development

15 Jul 2021

These notes were taken while studying using Mike Wheeler's Salesforce Courses.

Salesforce DX is built with package-based development in mind
- Org-based development - source of truth is production org

Package-based development - source of truth is package
- Benefits: better reusability, better version history tracking, better dependency tracking
- Useful for consulting companies, 3rd party app developers, companies that maintain multiple Salesforce orgs, etc
- Benefits less obvious for brand new orgs, but all Salesforce orgs grow
  - Will eventually result in unwanted dependencies/constraints

Salesforce DX uses Second Generation packages that are different than usual managed packages most admins deal with declaratively
- Help article comparing gen 1 and gen 2

Salesforce developer instructions for these steps here
First step when setting up a package is to register a namespace. AW completed this step in a second org.
- Setup > Quick Find > “package” > Package Manager > Edit > Continue
  - Select a Namespace Prefix (1-15 character alphanumeric ID unique across all orgs)
Second step is to turn on my domain
- Setup > Quick Find > “my domain”
  - My DevHub org already had MyDomain enabled. I had to change it to be able to access “Namespace Registries”

… 4 minutes in - unable to find the “Namespace Registries” tab