This document discusses Salesforce DX (sfdx), a new way to develop and manage Salesforce apps across their entire lifecycle. It outlines the goals of introducing sfdx which include discovering the new developer experience and taking a walkthrough of a simple use case. The document then explains what sfdx is, why it was created by solving issues with developer sandboxes, and how it can be used with tools like the CLI and commands like force:source:push. Finally, it provides an overview of how a sample use case would work, from retrieving and converting metadata to querying data and pushing/pulling from a repository.

1. Salesforce DX
abdelhakim.mouttaqui@gmail.com
@adbelhakim
https://www.linkedin.com/in/abdelhakimmouttaqui/
Abdelhakim Mouttaqui
Technical Architect & Force.com Developer
Casablanca – Oct 11th 2017

2. Goals and Audience
Discovering a brand new Salesforce Developer eXperience
Taking a simple use case’s walk-through steps
 Laying foundations for future more detailed DX events
Needed an intermediate sfdc experience
Events  Platform Basics talk

3. [What] sfdx
A new way to manage and develop apps across their entire lifecycle
 Source-driven development of code
 Team collaboration with governance
 Externalizing metadata
 Letting developers use their modern tools
 The “source of truth” shifts into a VCS
 New experiences, including the use of Heroku Flow to drive both CI and CD

4. [Why] sfdx
Solving developer sandbox quick/light rollback for canceled task
 Lightening developer sandbox setting up time loss
Simulating and testing apps on orgs with different features (compared with the “classic” dev
sandbox)
 Creating use-specific orgs for demo purposes

5. [Why] sfdx
CI scenarios : automated testing (e.g. with Jenkins) and optional further deploy to another
sandbox

6. [How] sfdx
Repository
creation
Local
Development
Pushing to
Scratch org
Optional
pulling
Pushing to a
sandbox or
testing env
Pushing to
remote
repository
Destroying
scratch org

7. Tools - prerequisites
Node JS
 Git
 Heroku/SFDX CLI

8. Tools: CLI – Commands Overview
sfdx force --help
sfdx force:project:create --projectname milanosfdug
sfdx force:mdapi:retrieve --unpackaged ./milanodug/package.xml --retrievetargetdir
./milanodug/retrieved

9. Use case - Big Picture
Retrieving Converting Developing Loading/Modeling Pushing

10. sfdx force:mdapi:retrieve
sfdx force:mdapi:convert
Retrieving and Converting
>> Setting up a package.xml file
>> Setting up a target folders for retrieved metadata
>> Taking action by CLI

11. sfdx force:auth:web:login
sfdx force:org:create
sfdx force:org:create
sfdx force:config:list
sfdx force:alias:set
Authorizing, creating a scratch org, config and alias settings
>> Authorizing our devhub (or another org, e.g. for using force:mdapi
 scratch orgs not manageable)
>> Check configs
>> Creating a new scratch org ( + defaultusername and scratch-
def.json)
>> Showing scratch orgs on Env Hub
>> Re-Check configs
>> Aliases : list, set and how to use them

12. sfdx force:source:status
sfdx force:source:push
Checking status and first push
>> Checking source status
>> Perfoming the first push

13. sfdx force:data:bulk:upsert
sfdx force:data:soql:query
sfdx
force:schema:sobject:describe
Developing, Loading, Querying
>> Editing metadata locally
>> Loading records from csv
>> Querying data

14. sfdx force:source:pull --force
sfdx force:source:push –-
force
git commit
git push
Push/Pull, conflicts, remote pushing
>> Pushing local edited files
>> Pulling remote changes
>> Solving conflict
>> Pushing to a remote repository
>> Destroying the scratch org

15. Demo

16. Thank Y u