Deployment FAQs

Is it possible to transfer Analytics Dataset Metadata, Dashboards, and Dataflows from one Salesforce Org to another using AutoRABIT?

Yes, AutoRABIT can move Analytics Components Metadata, Dashboards, and Dataflows from one Salesforce Org to another Org and the data will be available under the Wave Components list.

When you want to deploy the Analytics data, make sure you have enabled Tableau CRM in your Source Org and assigned permissions to your user record page through the permission set.

To enable the Tableau CRM in your Salesforce Org, follow these steps:

1. Log in to your Salesforce account.

2. Go to Salesforce Setup and enter Analytics in the Quick Find / Search field.

3. Select Getting Started.

4. Click Enable Tableau CRM.

Before you enable this option, you must have a license for the Analytics platform and this permission in your AutoRABIT profile.

To learn more about how to set up the Analytics Platform, refer to: https://blog.bessereau.eu/assets/pdfs/bi_admin_guide_setup.pdf

How can I make the metadata components (ex: ReportType) available for commit and deployment?

Go to the 'My Salesforce Settings' section of the My Account page to activate the metadata components. After that, select the metadata types you want to include in the excluded metadata types.

Why am I unable to retrieve metadata components during deployment?

If you cannot retrieve the components in ARM, although the components are available in Salesforce Org, check for the Salesforce API version from which you're deploying. You can look for the Salesforce API configured for your account under Admin > My Account > My Salesforce Settings section.

Why am I unable to access my Salesforce Production org?

1. When registering your production org, double-check the credentials.

2. Create a new API token for your Salesforce organization and re-enter your credentials with the new API token.

Why does my deployment from one sandbox to another fail without errors?

This commonly occurs when the Salesforce API version in your ARM application is incorrectly configured. You must upgrade the API source flow in your Salesforce org to the most recent version and maintain the same Salesforce version in ARM. To do so, go to Admin > My Account > My Salesforce Settings and update the API version.

Why am I unable to use AutoRABIT to deploy changes made to standard Salesforce fields?

One of the prominent causes is when the standard value set is not included in the commit. The deployment validation will succeed if you include it in addition to the standard field while committing.

When it's a standard field, we recommend including the Standard Value Set and selecting metadata from the picklist option. When it's a custom field, we recommend including the custom field.

Why does my deployment not appear in the target org when I run CI Jobs in AutoRABIT?

You are unable to see your deployment in the target org if the CI job was configured with the remove system and user permissions. Run the deployment while unchecking the user permissions option to resolve the issue.

When selecting the Autodraft features to commit the changes, why are some components missing?

This usually happens if you have used the filter with the most recent modified date rather than the source org's last modified date during the EZ-Commit process.

How do I use ARM to deploy case assignment rules?

Go to the Deployment module and select the case assignment rule during the metadata retrieval process to pick the rules. Errors commonly encountered due to Salesforce issues are listed at the top of this page.

Where can I find the standard picklist values for my deployments in AutoRABIT?

You can see the standard picklist fields under standard value set metadata.

Why am I unable to deploy the profile change from the version control repo to my target sandbox using a single revision?

Select the following checkboxes after picking up the required metadata and the profile members:

• Commit Options for Profile: This option allows you to commit settings for a full profile operation.

• Commit Access Settings for selected metadata (Profiles ONLY): This allows you to perform the commit operation based on the Profiles available only for the selected metadata.

Can CI Jobs be deployed using the "Run Tests Based On Changes" option if some of the LWC components do not have test classes?

Yes, even if one of the LWC components does not have test classes, you can deploy by selecting "Run Tests Based On Changes" because the test is run on the existing test classes for the change-relevant components. Click here for more detailed information about deployment configurations.

Why are deployments based on revisions from a version control branch to my target environment failing?

This occurs when the metadata folder path in the VC repository section is not configured. This problem will not occur once the .src path has been configured. For detailed information about how to configure the VC repository, click here.

Why don't I see the Release Label I created in the dropdown when performing a New Deployment?

It could be due to one of the following reasons:

• You have created a release label in ARM version 22.2 or older.

• You did not select the Create package manifest for Deployment checkbox while creating the release label in ARM 22.3.

• You selected the Create package manifest for Deployment checkbox, but the package preparation failed.

All of these problems can be solved by going to the Release Label Summary screen and clicking on Create Artifact for the respective release label. Once this is successful, the release label will be visible on the New Deployment page.

Why did the deployment fail without any error message?

To resolve this issue, please reauthenticate the Salesforce org and perform the deployment again. If the issue continues, please contact our support team.

Why is ARM not picking the latest activated version of the record trigger flow?

If you are trying to retrieve a recently updated Flow and not getting the latest metadata in the review artifact, modify the Salesforce Metadata API selected for the flow to the latest version, then retry the metadata retrieval. This time, you should see the latest metadata of the flow.

Why is deployment on the Salesforce org through CI Job failing with an error?

Change the baseline revision under CI jobs, then perform the deployment again. This should resolve the issue.

Why did the Release Label Merge fail with an error message on validation deployment?

One of the revisions in that Release Label may have duplicate values for the Layout file, as it could not pick the delta, so the validation failed. To resolve this:

1. Turn off On Successful Mock Deployment in the merge criteria and proceed with the merge, even though you have the validation deployment failure on the layout file.

2. Then manually modify the layout file on the target branch by removing the duplicate entries and triggering the CI Job deployment.

3. We recommend the same steps to avoid duplicates if you move changes into the Prod branch.

While trying to deploy a profile from our development org to the UAT org using the Profile Manager option, why is the profile not being deployed correctly to the UAT org?

This type of issue can occur if you have a profile in your UAT org and want to deploy it to the clone org, but the profile does not exist in your target org. We recommend using the Full Profile option in the Deployment module to resolve this. Then trigger the deployment again; the profile should successfully deploy to your target org.

Why did the quick deploy fail in ARM?

Quick Deploy may have failed due to the Metadata API version. Please update the Metadata API to the latest version and then perform the deployment again.

What does the 'Ignore Missing Visibility Settings' option do, and how does it affect the Deployment?

The 'Ignore Missing Visibility Settings' option refactors the Profiles/Permissions metadata. If users enable this option, the metadata that does not exist in the target org members' access settings/permissions will be removed from the package to reduce deployment failures. The following permissions are skipped if they're missing from the destination org:

• applicationVisibilities

• classAccesses

• customMetadataTypeAccesses

• fieldPermissions

• flowAccesses

• layoutAssignments

• objectPermissions

• page accesses

• recordTypeVisibilities

• tabVisibilities

Limitation

This option only works for List metadata-retrieved components. List the metadata from the workbench to view the metadata types.

Why does the Deployment appear as 'Failed' in ARM despite being successful in Salesforce?

If a deployment was successful in Salesforce but failed in ARM, this may be a Salesforce permission issue.

Please follow the troubleshooting steps given by Salesforce to enable the Exempt from Transaction Security permission: https://issues.salesforce.com/issue/a028c00000gAwsxAAC/intermittent-transaction-security-policy-error-while-login-or-making-api-calls-to-salesforce-we-cant-complete-the-action-because-enabled-transaction

Various Deployment sources and their functionalities:

1. Deployment via Commit Label: The entire files from the most recent revision under the commit label will be packaged together. Example: The entire profile will be part of the deployment.

2. Deployment via Single Revision: The delta change of the revision will be packaged. Example: If file permissions are included in the revision, only the file permissions will be considered as part of the change.

Can I deploy standard fields throughout ARM?

Often, users who are having issues deploying HTML reports in AutoRABIT are not aware of an SFDC limitation. Unfortunately, AutoRABIT cannot deploy standard fields because they cannot be edited in Salesforce. They are restricted from the SFDC side. You can commit standard fields but cannot deploy them.

Why are deployments failing when using the legacy Vlocity Components options?

The root cause of this issue is a change in how Salesforce handles Vlocity components. Vlocity has been fully integrated into the Salesforce platform under the name OmniStudio, and its components are now treated as standard Salesforce metadata types (e.g., OmniScript, OmniUiCard).

The special 'Vlocity components' selection within ARM is a legacy feature designed for the older, pre-integration version of Vlocity. Attempting to use this deprecated feature for a modern OmniStudio-enabled org will cause the deployment to fail silently, as the underlying APIs and metadata structure have changed.

Resolution: To successfully commit and deploy Vlocity/OmniStudio components, you must treat them as standard Salesforce metadata and not use the legacy 'Vlocity components' option.

Correct Procedure:

1. Do Not Use the 'Vlocity Components' Option: In your commit or deployment process, ignore and do not select the specific 'Vlocity components' checkbox or deployment type.

2. Select Standard Salesforce Metadata: Instead, use the standard metadata selection process (e.g., in an EZ-Commit or during CI Job setup).

3. Include OmniStudio Metadata Types: Select the appropriate standard Salesforce metadata types that correspond to your OmniStudio changes. Common examples include:

   • OmniScript

   • OmniUiCard (for FlexCards)

   • OmniDataTransform (for DataRaptors)

   • OmniIntegrationProcedure

By including these components as standard metadata, your Vlocity/OmniStudio changes will be correctly retrieved and deployed to your target branch or org using your standard ARM workflow.