DevOps

#SalesforceWinter24 – Select Who Has Access to the Sandbox When Creating or Refreshing

/ ,

#1MinuteTip #SalesforceWinter24 You can now explicitly specify who should have access to the sandbox when creating or refreshing a sandbox. This selective access is given through the public group.

The email addresses for the users included in the group remain in their original format (without .invalid appended to it) and don’t need to be modified.

Product Area: Development -> Development Environments

Select Who Has Access to the Sandbox When Creating or Refreshing

References & Useful URLs

Want to Receive these Tips in your Inbox?

Finding it overwhelming to keep pace with Salesforce’s new release features? Try our “1 Day 1 Tip 1 Minute” emails, where you are going to get 1 tip every day that won’t take more than a minute to read. To find out more and subscribe please click here.

Now Available Salesforce CLI “sf” v2

/ ,

#1MinuteTip The Salesforce CLI is one of the most important development tools in Salesforce ecosystem. The CLI is Salesforce Developers’ everyday companion for building, testing, deploying, and more. Salesforce announced the general availability of Salesforce CLI v2 in July 2023.

The main improvement that I liked in v2 is that the command syntax has now become simple and easy to use. For example, with sfdx, you needed to type the following to the list of all Salesforce orgs that you are connected to. 

sfdx force:org:list

But now with v2, the syntax has become simple and more flexible. For example, you can type any of the following to get the list of the orgs. You do not necessarily need to type the command in the exact order.

sf org list
sf list org
Salesforce CLI v2
Image Source: Salesforce Developer Blog Post (link below)

References & Useful URLs

Generate Package.xml for your Salesforce Org with a single command

/

#1MinuteTip In Salesforce, the package.xml file serves as the manifest file for both deploying components and retrieving them from a Salesforce Org. It specifies the components that you wish to deploy or retrieve.

Here is a single command in Salesforce CLI that will generate the package.xml file for you.

sf project generate manifest --from-org <salesforce-org-alias>
sf project generate manifest

And here is the package.xml file that the command will generate for you.

package.xml generated by Salesforce CLI

You can use –type to specify the type of manifest you want to create such as the standard package.xml or destructiveChanges.xml to delete metadata.

You can also specify the metadata components that should be included in the manifest file. E.g. ApexClass, CustomObject etc.

Please refer to the following link for the reference document on this command.

References & Useful URLs

A Video Series on Salesforce DevOps Essentials

/

#1MinuteTip Here is a series of videos on DevOps Essentials in Salesforce. One of the most useful set of videos you can watch on DevOps in Salesforce.

  1. Defining Your Pipeline: In the 1st episode, understand the different types of orgs that can be used for development and testing features before they go into production. Salesforce also shares the considerations to take into account when defining your pipeline stages and deciding the orgs to use on each stage.
  2. Adopting Source Control: In this second episode of the DevOps Essentials, Salesforce talks about what source control is and how you can adopt it in your Salesforce projects. They also share considerations to define your git branching model and to map it to your pipeline.
  3. Setting Up an Org for Development: In the 3rd episode learn Salesforce org setup for development: sandboxes, scratch orgs, metadata, users, permissions, packages, automation, and more!
  4. Salesforce CLI and VS Code: In 4th episode learn how to use the Salesforce development tools to deploy applications to source-tracked and non-source-tracked orgs following version control best practices.
  5. Continuous Integration: In this episode learn how implementing continuous integration in your Salesforce projects will reduce conflicts, ensure quality and prevent bugs, optimizing the development lifecycle.
  6. Promoting Changes Between Environments: 6th episode covers how to promote changes to your source version control system using git, and promote changes with the Salesforce CLI using the different deployment approaches, Full, Delta, and Unlocked Packages.
Salesforce DevOps Essentials

References & Useful URLs

#SalesforceSpring23 – Grant Explicit Access to Sandbox While Creating

/ ,

#1MinuteTip #SalesforceSpring23 You can now define who will have access to the sandbox, while creating the sandbox.

With selective sandbox access, grant access only to required users. It also removes the additional step for a Salesforce admin to change the user email address back to the original format. If you don’t want to match the access currently defined in the source org, you can create a public group to grant access to a subset of users.

Product Area: Development – Development Environments

Grant Explicit Access to Sandbox

If you don’t see the option “Sandbox Access User Group”, while creating the sandbox in your production org, please log a case with Salesforce.

References & Useful URLs

  • For Related Spring ’23 Release Note Article – Click Here

Want to Receive these Tips in your Inbox?

Finding it overwhelming to keep pace with Salesforce’s new release features? Try our “1 Day 1 Tip 1 Minute” emails, where you are going to get 1 tip every day that won’t take more than a minute to read. To find out more and subscribe please click here.

Scroll to Top
Introducing All Access Pass
Check Details
SUBSCRIBE NOW