Dale

Metadata changes on the fly

“As a purely declarative consultant with no coding experience, Snapshot helps >me quickly summarize the evolution of my clients’ orgs and identify opportunities for their optimization and growth.”

— Salesforce Consultant, Dale Ziegler.

 

“Snapshot gives us a core toolset to handle a wide range of sandbox instances”

 

 


Build Visual Deployment Pipelines For Salesforce

Deployment Pipeline

The Metazoa Snapshot Change and Release Management product provides drag and drop tools that enable Salesforce administrators to build highly visual deployment pipelines. Administrators can create any number of deployment pipelines, switch between different pipelines as needed, and share the pipelines with team members.

Visual Pipeline

Build Visual Deployment Pipelines For Salesforce

Snapshot provides tools to create a visual map of your Salesforce release environment. Developer Projects can be connected to Salesforce Sandboxes, which in turn can be connected to the Production Org. This visual map can be changed over time to support a wide variety of release management scenarios. All of the snapshots and Metadata deployments on the desktop can be scheduled and automated as needed. The Snapshot desktop provides a visual guide to Metadata flows from the source to destination. Your implementation might be more or less detailed depending on your process and needs. The Snapshot desktop provides a flexible way to rewire your release environment over time and accommodate new projects and reports.

The workspaces can be shared and locked, preventing any changes to the release management process. In this manner, Administrators can specify the Orgs and Projects that other developers or consultants should be focused on. Super Admins can specify the types of data and Metadata that are allowed to be deployed in the release flow. Super Admins can also set up Code Quality Gateways for developers. The visual workspaces can also be archived, to provide a permanent record of the release management process for compliance or documentation.

Learn More

Here are some helpful links with more information about Deployment Pipelines:

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to schedule a demo.


Roll Back Salesforce Metadata Deployments

Roll Back Deployment

The Metazoa Snapshot Change and Release Management product can automatically roll back Salesforce Metadata deployments to any previous state. This is a key technology for backing up and restoring an Org after undesirable customizations are detected. Salesforce administrators can see the differences in any Org over time, and restore the Org as needed.

Roll Back Deployment

Roll Back Salesforce Metadata Deployments

Snapshot provides powerful tools for restoring a Salesforce Org to any previous state. You will need to be sure that your Org has a Time Series of metadata backups. This capability is easy to set up in the Snapshot product. When you need to restore Metadata to any Salesforce Org, the Roll Back Deployment dialog has options that make this automatic.

The Roll Back Deployment dialog uses time series snapshot data to restore the destination org to an earlier date. Any one of the earlier snapshots can be selected as the source. The destination org can be refreshed and continually compared to the source until everything has been restored. The Calculate Differences button will calculate all of the differences in the source and destination org to assemble the Create and Delete Job List. In some situations, you will get better results with the Swap Create and Delete button. In that case, the time series of earlier Job Lists are merged and flipped. Often you will only need to restore some part of a deployment. This dialog documents all of the changes and the historical Job Lists in one interface. The menu at the top of the Roll Back Deployment Metadata dialog provides three options:

  • Validating Deployment – This option will check for errors without making changes. The deployment is simulated, and no changes are actually made to your Salesforce org. All success and error messages are displayed in the results box.
  • Transactional Deployment — This option will roll back all changes if there is an error. If there are any errors, the entire deployment is rolled back; otherwise all assets will be migrated. All success and error messages are displayed in the results box.
  • Partial Deployment — This option will change everything possible and ignore errors. Assets that cause errors are rolled back, but other assets continue to deploy unless there are cascading errors. This option is not available for production orgs.

When you are deploying assets to a production org, you must use a Transactional Deployment. This option has the advantage of rolling back all changes if there is an error. Sometimes for more complex migrations, you will need to make multiple deployments.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to schedule a demo.


Continuous Integration With Salesforce and Github

Continuous Integration

Continuous integration is a software development practice in which developers regularly integrate their code changes into a source code repository. Automated builds and tests run before or after developers check in their changes. The Metazoa Snapshot Change and Release Management product provides CI tools for Salesforce administrators and developers.

Continuous Integration

Continuous Integration With Salesforce and Github

Metazoa Snapshot provides sophisticated and flexible tools for continuously keeping Salesforce accounts, developer projects, and content repositories synchronized. A wide variety of different use cases can be implemented by simply connecting items on the desktop and turning on continuous integration. Developer projects and content repositories can be in either Metadata API or Salesforce DX format.

There are two main styles of continuous integration to choose from. The first is triggered when the source Salesforce Org or developer project changes. In this case selected metadata types are moved from the source to the destination. The second watches for changes in deployment history. When a new deployment makes changes to the source Salesforce Org or developer project, then the same deployment is replayed to the destination.

Your local Salesforce DX or Metadata API project can be optionally connected to a content repository. In this case, the editing tools for the local project are no longer displayed, because the source of the metadata files is now the remote repository. The project folder is still used to store a local copy of the files. Developers can switch the interface back and forth to work on the local project or the content repository as needed. When the project is connected to a content repository the files in the developer project will be replaced when a snapshot is taken.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or contact us to


Synchronize Salesforce Orgs and Github Repositories

Synchronize Salesforce and Github

The Metazoa Snapshot Change and Release Management product provides tools that enable developers and administrators to synchronize Salesforce Orgs with other Salesforce Orgs, local Developer Projects with Salesforce Orgs, and Salesforce Orgs with online Repositories such as Github, Bitbucket, SVN, and Team Foundation Server.

Synchronize Salesforce and Github

Synchronize Salesforce Orgs and Github Repositories

Metazoa Snapshot provides sophisticated and flexible tools for continuously keeping Salesforce accounts, developer projects, and content repositories synchronized. A wide variety of different use cases can be implemented by simply connecting items on the desktop and turning on continuous integration. Developer projects and content repositories can be in either Metadata API or Salesforce DX format.

There are two main styles of continuous integration to choose from. The first is triggered when the source Salesforce Org or developer project changes. In this case selected metadata types are moved from the source to the destination. The second watches for changes in deployment history. When a new deployment makes changes to the source Salesforce Org or developer project, then the same deployment is replayed to the destination.

Your local Salesforce DX or Metadata API project can be optionally connected to a content repository. In this case, the editing tools for the local project are no longer displayed, because the source of the metadata files is now the remote repository. The project folder is still used to store a local copy of the files. Developers can switch the interface back and forth to work on the local project or the content repository as needed. When the project is connected to a content repository the files in the developer project will be replaced when a snapshot is taken.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to schedule a demo.


Push and Pull Source with Salesforce DX Scratch Orgs

Push and Pull Source

Salesforce DX can be used to create any number of Scratch Orgs in your Dev Hub. The Metazoa Snapshot Change and Release Management product can launch these Scratch Orgs in the browser, and also Push and Pull Source from any Salesforce DX Scratch Org. This technology enables developers to create Source Driven Projects on their local machine with Salesforce DX.

Developer Project

Push and Pull Source with Salesforce DX Scratch Orgs

After you do an initial push, Salesforce DX tracks the changes between your local file system and your Scratch Org. If you change your Scratch Org, you usually want to pull those changes to your local project to keep both in sync. During development, you change files locally in your file system and change the Scratch Org using the builders and editors that Salesforce supplies. Usually, these changes don’t cause a conflict and involve unique files.

Metazoa Snapshot has visual tools to Push and Pull Source from a Salesforce DX Scratch Org. You can select an existing Scratch Org or create a new one at any time. The tools display information about local assets in the project folder that could be pushed to the Scratch Org, and remote assets in the Scratch Org that could be pulled down. The Source Push button will deploy any local adds to the currently selected Scratch Org. The status list will update after the metadata deployment. The Source Pull button will retrieve any remote adds from the currently selected Scratch Org. The status list will update after the Metadata is retrieved and the local project is updated.

The Push and Pull Source command works with Scratch Orgs only. If you’re synchronizing source to any other Org, use the Metadata API. By default, only changed source is synced back to your project. The pull command does not handle merges. Projects and Scratch Orgs are meant to be used by one developer. Therefore, we don’t anticipate file conflicts or the need to merge. However, if the pull command detects a conflict, it terminates the operation and displays the conflict information. The short movie below shows how to Push and Pull Source to a Salesforce DX Scratch Org.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to schedule a demo.


Create Unlocked Packages with Salesforce DX Projects

Unlocked Packages

Salesforce DX projects can be used to create Unlocked Packages in your Dev Hub. These Unlocked Packages and Package Versions can then be installed in any Scratch Org, Salesforce Sandbox, or Developer Edition Org. Unlocked Packages are the key technology for organizing your unpackaged Metadata and reducing the complexity of your Org.

Create Unlocked Packages

Create Unlocked Packages with Salesforce DX Projects

Most Salesforce Orgs contain a sea of unpackaged metadata. Some customizations are made by hand with the Setup Menu, others are created with Change Sets or the Metadata API. Unpackaged customizations can pile up over time and make the org difficult to manage. Too many customizations can result in slow performance, reduced agility, sluggish adoption, and added complexity. Moving assets into Unlocked Packages can solve this problem and add much needed structure to your Salesforce account.

There are significant benefits to adopting Salesforce DX and Unlocked Packages. Bugs and problems are isolated to the package instead of being spread across the entire org. When a project needs to be upgraded or replaced, the package makes entangled assets easier to identify. Packages are the foundation for agile development, enabling smaller groups of developers to focus on more isolated sections of code. Packages can be individually tested in a Scratch Org or developer account. Modular packages can be used to enable multiple orgs and partners. Packages lower cost, increase flexibility, reduce complexity, and improve time to production.

Metazoa Snapshot has powerful tools to convert a Salesforce DX project into an Unlocked Package that will be stored in the Dev Hub. Then an administrator can install these Packages and Package Version into any Salesforce Org. When you have built Salesforce DX projects that are working correctly, you can create packages in your Dev Hub and then install the packages into Sandboxes for testing or Production for deployment. The Metadata API can be used to deploy other unpackaged assets. You can also use the Metadata API to move Second-Generation Unlocked Packages into Production. This has the advantage of automatic roll-back if there is an error.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to schedule a demo.


Backup and Restore Salesforce Orgs for Disaster Recovery

Disaster Recovery

Companies need to archive the data and Metadata in their Salesforce Orgs for compliance and security. The Metazoa Snapshot Change and Release Management product provides powerful tools to backup and restore Salesforce Orgs for disaster recovery. The data and Metadata can be restored in the event of data loss or customization errors.

Roll Back Deployment

Backup and Restore Salesforce Orgs for Disaster Recovery

Many large companies have established policies for disaster recovery. Companies need the ability to track Org changes over time and the capability to restore the Org to any previous state. Companies in the financial and health sectors are regulated by state, federal, and foreign governments. Various regulations include SOX, PCI-DSS, GLBA, HIPAA, HCQIA, CHIP, HRRP, PSQIA, ACA, FISMA, PCI-DSS, FERPA, and most recently GDPR. Regulatory compliance requires information backup policies and planning for disaster recovery.

The customizations in a Salesforce Org provide crucial information about how the Org is structured. Almost all of this information can be captured with the Metadata API, which returns over 200 different XML documents that describe all of the customizations in a Salesforce Org. These XML documents cover everything you can imagine, such as Objects, Tabs, Applications, Apex Code, Profiles, and Page Layouts. Salesforce data can also be backed up as needed. The data in a Salesforce Org can be accessed through the SOAP API and SOQL Queries.

The Metazoa Snapshot Change and Release Management product can be used to backup the data and Metadata in any Salesforce Org. The information can be saved as XML files on network hard disks or as Salesforce Content documents. Snapshot can also schedule regular backups that create a picture of how the Org changes over time. In the event of data loss or disaster recovery, Snapshot can restore the data and Metadata in the Org from the archived files. In some cases only a partial restoration is needed. For example, a specific customization in a Salesforce Org can be rolled back to a previous state.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to schedule a demo.


Migrate Relational Data Between Salesforce Orgs

Data Migration

The Metazoa Snapshot Change and Release Management product can move connected sets of data between Salesforce Orgs. Unlike Data Loader, Snapshot keeps all relationships between Objects intact. Administrators can migrate data between Salesforce Orgs for testing, development, or backup purposes. Snapshot also supports CSV file import to bring in datasets from external systems such as Oracle or SAP.

Build Datasets

Migrate Relational Data Between Salesforce Orgs

Snapshot provides powerful tools for migrating connected sets of data between Salesforce Orgs. This capability is useful for backing up data, refreshing Sandboxes, merging Orgs, and populating Orgs with test data for application development. The Bulk API is used for all transactions to ensure that very large Datasets can be moved efficiently. We have moved hundreds of thousands of records while testing the data migration tools in Snapshot.

When an administrator migrates data between Salesforce Orgs, all of the internal relationships are preserved. External references in the Dataset are also connected to matching objects on the destination. Snapshot also supports CSV file import to bring in datasets from external systems and for creating datasets with a spreadsheet editor. Snapshot can scramble selected fields to maintain data privacy and remap field names for any destination Org.

When you select the Deployment Arrow between any two connected Snapshots, the Options Menu will display various commands. The second set of options will be to Build, Import, and Migrate Datasets. The option to Build a Dataset will use the source Salesforce org to download multiple records in the form of XML files to your local machine. The option to Import a Dataset will use CSV or XML files from any source to create a new Dataset as well. Lastly, the option to Migrate a Dataset will insert and update records from the selected Dataset into the destination Salesforce Org. Watch the short movie below to learn more about the relational data migration capabilities in Snapshot.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to schedule a demo.


Splitting and Merging Complex Salesforce Orgs

Splitting and Merging Orgs

When companies merge or divide, Salesforce administrators may be faced with the difficult job of cloning, merging, or splitting complex Salesforce Orgs. The Metazoa Snapshot Change and Release Management product has powerful data and Metadata comparison and deployment tools that can assist with this task.

Deploy Metadata

Splitting and Merging Complex Salesforce Orgs

Snapshot provides highly visual tools for retrieving Metadata from any Salesforce account or developer repository. Metadata assets can be moved into a partial or full Sandbox, and after quality assurance and user acceptance testing, deployed into a production Org. As part of the migration process, Snapshot provides two dozen security and compliance reports that help you analyze Metadata structure, data usage, and account security. These tools can be especially helpful when Salesforce administrators are assigned the difficult task of cloning, merging, or splitting Salesforce Orgs.

When moving Metadata between any two Orgs, you will first need to create a source and destination Snapshot. Then you can double-click the deployment arrow to move metadata from the source to the destination Org. Next, you will need to build Job Lists for the metadata assets that you want to create and delete. Because of Metadata dependencies, you may want to move assets in a particular order. Here are the best practices for moving Metadata types between Orgs:

1. Objects
2. Apex Classes
3. Apex Components
4. Apex Pages
5. Apex Triggers
6. S-Controls
7. Page Layouts
8. Static Resources
9. Letterheads
10. Workflows
11. Report Types
12. Home Page Web Links
13. Home Page Components
14. Home Page Layouts
15. Custom Tabs
16. Custom Labels
17. Custom Applications
18. Custom Object Translations
19. Custom Sites
20. Profiles
21. Permission Sets

You can use the Snapshot Metadata Comparison report to verify that the required Metadata Types are the same in any two Orgs. Additional Metadata deployments may be required to make the Orgs have the same architecture. When the Metadata is looking good, you can start to move Custom Objects as well. The Snapshot Build Datasets and Migrate Datasets capability can move connected sets of data between Orgs as needed. The short movie below shows how to use the Take Snapshot tool and the Metadata Deployment interface to move assets between Salesforce Orgs.

Snapshot provides powerful tools for Salesforce Administrators that help manage the change and release process, visualize org complexity, improve security and compliance, and lower the total cost of Org ownership. Visit the AppExchange to start a 14 day free trial or click the button below to.