Learn MOAR with Summer ’20 Release Highlights for Developers

Learn MOAR

It’s easy to get started. First, dive into the Trailhead trailmixes with key release highlights for Admins, Developers, or both! (Don’t forget to hit Follow.)

Then, check in over the next few days to read our favorite Summer ’20 Release features on both the Salesforce Admin and Salesforce Developer blogs.

Be sure to follow and complete the trailmix by July 31, 2020 to earn a special community badge and unlock a $10 donation to Bibliothèques Sans Frontières (Libraries Without Borders), a nonprofit that works to ensure all people have equal access to information, education and cultural resources, regardless of their circumstances.

 

 

Dive into developer features

The Summer ’20 Release brings two exciting additions — in beta — for every Salesforce Developer and Admin: source tracking in sandboxes, and org dependent packaging.

Many of you know the capability of using source tracking in scratch orgs. Using the `sfdx force:source:pull` commands, you can get all changed data from a scratch org into your local Salesforce DX project, and with the `sfdx force:source:push` command you can push changed metadata to a scratch org. Now with this new beta feature, you’ll be able to use these commands in Developer and Developer Pro Sandboxes. This simplifies the way you track changes in sandboxes, and how they’re brought together in your local projects. If you need a refresher, we recently posted a deep dive into source tracked projects that applies to scratch orgs and source tracked sandboxes.

 

 

Org dependent packaging is another great feature for developers. When you build (unlocked) second-generation packages today, you need all the metadata for that package locally in your DX project. That includes dependent metadata. For example, when you refer to a custom object in your Apex code, you will also need the objects metadata in your project. With the new `orgdependent` feature, available in the pre-release version of the Salesforce CLI, you can create these packages without the dependent metadata. So compared to the current behavior, the metadata validation changed from a build time validation to a runtime (aka: installation) validation. This is an important step forward, as you can start to adapt packaging as needed, without having to untangle your org right away.

#LearnMOAR and share

Share what you love about the Summer ’20 Release with the #LearnMOAR hashtag. Also, make sure to watch the replay of Release Readiness Live.

About the author

René Winkelmeyer works as an Architect for Developer Evangelism at Salesforce. He focuses on enterprise integrations, Lightning, and all the other cool stuff that you can do with the Salesforce Platform. Java, JavaScript, Swift, and node.js are often his friends.