How To Utilize Source-Tracked Sandboxes

Salesforce source-tracked sandboxes are a type of sandbox that supports source-driven development methodologies. Sandboxes in Salesforce are isolated environments that allow developers to build, test, and deploy changes without affecting the production instance.

The introduction of source-tracked sandboxes enhances the development process by providing a more structured and version-controlled approach.

Source-tracked sandboxes are designed to align with modern software development practices, such as using source control systems like Git.

🤝

They allow developers to track and manage their Salesforce metadata and configurations, enabling collaboration, versioning, and automated deployments.

Source-tracked sandboxes do come with limitations, including:

They do not contain production data

They only include metadata and source code.

Source-tracked sandboxes have storage limits, varying depending on the specific sandbox type

If the sandbox reaches its storage limit, it may impact your ability to deploy changes or add new components.

Source-tracked sandboxes are available in different types, such as Developer Sandboxes, Developer Pro Sandboxes, and Partial Copy Sandboxes

Each type has its own limitations in terms of features and capabilities.

Creating a source-tracked sandbox involves copying metadata from the production environment

This can be time-consuming.

There may be limitations on the number of licenses available or specific user permissions

This depends on the sandbox type.

Source-tracked sandboxes may present challenges

This is when multiple developers simultaneously work on the same project.

As source-tracked sandboxes do not contain actual data

This means that testing certain functionalities that rely on specific data conditions or volumes can be challenging.

Sandbox type

Description

Use cases

Advantages

Disadvantages

Partial sandbox

A sandbox environment that provides partial isolation or restrictions on system resources and functionality.

Testing specific components or features.

Isolating critical processes.

Controlled experimentation.

Offers some level of isolation and security.

Allows targeted testing and analysis.

Limited scope of isolation.

May not fully replicate production environments.

Potential for escaping the sandbox.

Full sandbox

A sandbox environment that provides complete isolation and restriction.

Running untrusted code or applications.

Evaluating potentially harmful files.

Analyzing unknown software behavior.

Protects the host system from potential threats.

Enables thorough testing and analysis.

Performance overhead due to complete isolation.

May require additional resources.

Potential for limitations on functionality.

Explore Source-Tracked Sandboxes With Hutte

Are you looking to utilize source-tracked sandboxes? Cut out time wastage by using Hutte.

👍

With Hutte, a web UI to SFDX that enables visual Salesforce version control, Salesforce sandboxes become a labor-saving development workflow. Hutte enables developers to easily create, modify, and delete sandboxes as needed.

To understand how Hutte works, start your free 30-day trial, or check out our demo below.

To kick things off, let’s start by setting up your first sandbox project through Hutte.

Setting Up A Sandbox Project

Connect A Salesforce Production Org

Authenticate your org with your Salesforce user to grant your Hutte project access to sandbox creation and metadata.

Connect A Git Repository With A SFDX Project

It can be an empty project or a local representation of your org's metadata. This is where you'll keep track of your sandbox development work.

You can now choose an existing sandbox from "Available Sandboxes," or create one by clicking "New."

Developing In Sandboxes

After setting up a sandbox project, you will find all existing sandboxes to your connected production org on the "Available Sandboxes" tab. You can also easily create new development sandboxes from the "New" button.

Hutte is truly one of the best tools that we use. Product owners, Salesforce solution architects, business analysts — anyone on our team can easily and visually accomplish the tasks that would otherwise take a lot of clicks, time, and coding.

Sebastian Lechner

Product Management Director of IPfolio
Clarivate

Source: Hutte

Before you start to work on a feature, use the "Add to Hutte" link appearing when you hover your sandboxes on the "Available Sandboxes" tab.

Switch to "Features" and hit "New."

Next, login to your sandbox from the "Login" button. Your first login might require setting up a two-factor authentication, following the on-screen instructions provided by Salesforce. You can then perform your work in your sandbox.

👀

Shortly after performing your changes in the org, they will become visible in Hutte (just remember to refresh your screen).

To carry on with your changes in Git, click "Pull changes." This creates a pull request. You can control its name and message in the "Pull Request" tab. As you continue to perform changes, your pull request gets updated and the timeline shows a chronological history of your changes.

Once you’re finished with your work, hit "Close." This allows a new feature to be created.

To deploy all changes that are part of a feature to your connected production org, use the simple “Deploy to Production" button.

Use Custom Buttons

Leverage the power of automation by making handy scripts available at your team member's fingertips. This will allow you to configure Hutte Custom Buttons in your sandbox projects.

🌱

A great use case example is allowing users to optionally load seed data into new dev sandboxes.

Sandboxes Available Anytime, Anywhere

🙌

Hutte makes it easy for every member of the product team to work with sandboxes – without learning Git and using the command line.

Automate sandbox scripts with our Custom Buttons. It can be a translation download or creating another user. Anything you can do with SFDX, you can add to your buttons.