Data Deployment

If you are getting the below errors during the deployment in ARM, follow the respective Salesforce article to get resolve the issues:

• For error: The layout Must Contain an item for the required layout field: IsnonStandard
  • Please refer to this article, https://developer.salesforce.com/forums/?id=906F00000008sDkIAI
• For error: Permission Import Personal Contacts depends on permission(s): create account, Create Contact, Edit Account, Edit Contact
  • Please refer to this article, https://developer.salesforce.com/forums/?id=906F00000008lFkIAI
• For error: Permissions Read All ServiceTerritory depends on permission(s): Read All OperatingHours
  • Please refer to this article, https://developer.salesforce.com/forums/?id=906F0000000AkbzIAC
    
    

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

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

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

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

1. Login 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 licence for the Analytics platform and this permission in your AutoRABIT profile.

To know more about how to setup Analytics Platform, refer: 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, deselect the metadata types that you want to include in the excluded metadata types.

Unable to retrieve metadata components during deployment

If you're not able to retrieve the components in ARM although the components are available in Salesforce Org, then check for the Salesforce API version on which you're perfroming the deployment. You can look for the Salesforce API configured for your account under Admin > My Account > My Salesforce Settings section.

I am unable to access my SF Production org

1. When registering your production org, double-check the credentials.
2. Create a new API token for your Salesforce organisation and re-enter your credentials together with the new API token.
   
   

When I try to deploy one sandbox to another sandbox, it fails without any errors?

This commonly occurs when the Salesforce API version in your ARM application is wrongly 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.

I'm unable to use AutoRABIT to deploy changes made to standard Salesforce fields.

One of the prominent causes would be that the standard value set was not included in the commit.
If you include it in addition to the standard field while committing, the deployment validation will succeed. When it's a standard field, we recommend include the Standard Value Set and selecting metadata from the picklist option, and 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 probably wouldn't be able to see your deployment in the target org because the CI job was configured with the remove system and user permissions.
To resolve the issue, run the deployment while unchecking the user permissions option.

When selecting the Autodraft features to commit the changes, some of the components are 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 the AutoRABIT to deploy case assignment rules?

Go to the Deployment module and select case assignment rule during the metadata retrieval process to pick the rules.

If you are getting below errors during the deployment in ARM, follow the respective Salesforce article to get resolve the issues:
• For error: The layout Must Contain an item for required layout field: IsnonStandard
Please refer this article, https://developer.salesforce.com/forums/?id=906F00000008sDkIAI

• For error: Permission Import Personal Contacts depends on permission(s): create account, Create Contact, Edit Account, Edit Contact
Please refer this article, https://developer.salesforce.com/forums/?id=906F00000008lFkIAI

• For error: Permissions Read All ServiceTerritory depends on permission(s): Read All OperatingHours
Please refer this article, https://developer.salesforce.com/forums/?id=906F0000000AkbzIAC

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

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

I am unable to deploy the profile change from the version control repo to my target sandbox using single revision.
Select the below checkboxes after picking up the required metadata and the profile members:

• Commit Options for Profile: This option allows you to choose commit settings either 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.
  
  

Is it possible to deploy CI Jobs 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 detail’s 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 detail information about how to configure the VC repository, click here.

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

If you don't see the release label while performing 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 check box while creating the release label in ARM 22.3.
• You selected the Create package manifest for Deployment check box but the package preparation failed.

All of these problems can be solved by simply 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.

When a custom field is deleted from a Standard Object, why is the entire object getting deleted during Deployment?

This is expected behavior. ARM deletes the object if there is no child present in the object at the time of commit. That is the reason the object is prepared as destructive in the deployment.