Salto

Salto for Salesforce - Overview

Salto for Salesforce CPQ - Overview

Connect your Salesforce Org

SFDX integration with Salto

This guide outlines how to implement CI/CD process tailored to your needs using Salto.

CI/CD the Salto way (for Salesforce and for everything else)

Salesforce FAQ

Support

Zalary Young

Dan Avigdor

Learn how to manage your Salesforce configuration with Salto.

Salto for Salesforce

Salesforce "Where is this used" functionality for standard and custom fields

"Where is this used" for fields in reports and dashboards

This article explains the behavior when deploying Flows with Salto, along with some considerations for managing flow versions.

Managing Salesforce Flows

Fetching Salesforce Installed Packages

Learn how to specify which Apex tests are run when deploying Salesforce changes

How to run Apex tests during Salesforce deployment

Impact Analysis for all salesforce metadata types

Supported Salesforce Types

CPQ triggers can fire during a data load and this may not be what you want

Why we recommend you disable CPQ triggers when deploying CPQ data

Salto can be used to treat CPQ data as metadata and to align this data across multiple Salesforce orgs. This article describes how to do so.

Treat CPQ Data As Metadata And Align Data Across Multiple Orgs

You can use Salto to seed CPQ data from production to a sandbox org for testing and development purposes.

How To Seed A Sandbox With CPQ Data

This article provides a detailed walkthrough for determining the number of records associated with specific types in Salesforce

How to count elements in Salesforce

Customize which records are fetched by Salto e.g. maxInstancesPerType

Limiting the number of Salesforce data records fetched

Guides

Suppressing deployment preview issues

Large deployments can fail due to a Salesforce limit on metadata deployments

The metadata deployment exceeded the maximum allowed size of 50MB

What this warning means and how to resolve it

Fetching from Salesforce ended with a warning: 'Data Records Not Fetched'

Guide to deploying Workflow Outbound Messages in Salesforce, with tips on fixing the ‘User Does Not Exist in Target’ error

How to Deploy Workflow Outbound Messages

Resolving Salesforce Field Type Errors in Salto Deployments

Error When Creating or Modifying a Field with an Unknown Type

Fix Task/Event Field Modification Errors in Salesforce

Error When Modifying a Field in Task or Event

When attempting to deploy a Salesforce flow, you may encounter an error message related to the API version

Resolving API Version Error in Deployment

Troubleshooting

This error occurs when you do a data deployment with a new picklist value

Unknown picklist value

Salesforce does not allow record type deletions through the API

Cannot delete record type

Salesforce doesn't allow Flow deletions through the API

Cannot delete flow

Changing the fullName of a Salto element is not supported

You cannot change the fullName property of an element

This account setting cannot be deployed unless the OWD is set to private

Account Owner Report Cannot be Enabled

Case Teams are not supported when deploying assignment rules

Deployment of case assignment rule that references a predefined case team is not supported

Duplicate Rules must be in sequential order

Not all elements from managed packages can be modified

Modifying an element from a managed package may not be allowed

Consider deploying this metadata type manually

DataCategoryGroup deployment may be destructive

Multi-currency Deployment Preview Errors

Installed packages cannot be added or modified through the API

Deployment Preview errors for Installed Packages

These objects/fields are assigned via feature license

Creation/Deletion of Standard Field/Object is not allowed

Object records are not included in check-only deployments

Data instances are not supported in Validation deployments

You must install or delete managed packages directly through the Salesforce UI

Installed packages cannot be added/deleted through Salto

Profiles being deployed may reference types which are not available in the target environment so Salto cleans them up before deploying