Deployment Using Version Control

This section is all about deploying the nCino data using Version Control

  1. Hover your mouse over the nCino module and click on the Deployment History option.

  1. Click on the Feature Deployment button.

  1. On the next screen, give the process a name and a brief description.

  2. In the SOURCE section, select Deployment From as 'Version Control.'

  3. Select your version control type.

  4. Select your repository and branch.

  5. Select the deployment type. There are three options to choose from:

    • Entire Branch: This option will fetch the feature migration templates configured on your branch. You'll be asked to choose the template and version when selecting the entire branch option.

    • Single Revision: This option will pull all of the versions from your repo, allowing you to choose which revision to use in the deployment.

    • Revision Range: This option allows you to specify a commit range from which the revisions are to be deployed.

  6. The object configuration section will render the selected objects and apply filters and mappings based on your selection.

  1. Choose your target org.

  1. There are various options that you can configure to your objects before you proceed with deployment:

    • Applied Mappings

    • Applied Filters

Applied Mapping

In this section, you can use an external ID in place of a related record's Salesforce record ID to relate or associate records to each other as you process an Upsert operation. For example, if Object B has a lookup field to another Object A, you can use the values in a field marked as an External ID on Object A to relate the two (Object B to Object A records).

In the Source field: Select your source field whose values will be populated in the destination External Id field.

In the Destination field: Select the required field from the destination org whose values will remain unique for all the records.

Important Note (About Applied Mappings):

  1. If there is no Lookup key and the name is set to External ID, AutoRABIT is still supported.

  2. Because the source for this is a CSV extract and not a salesforce org, all fields from the source sandbox will be fetched, regardless of the External ID in the Source column, whereas the source for Destination is a salesforce org.

Applied Filters

Such filters will be displayed here if any filter is applied to the objects.

Important Note: The dataset is already prepared at the time of the commit, so you can’t edit it at this point. However, if you like to edit the filter, use the feature: Deployment via Version Control using Salesforce org

Click on Deploy to proceed to the next screen. The next screen will display the list of deployment criteria that you can opt for before proceeding with deployment.

Deployment Settings

  1. Disable Workflow Rules: This option will deactivate the workflow rules associated with objects part of the deployment

  2. Disable Validation Rules: This option will deactivate the validation rules associated with objects part of the deployment

  3. Use Bulk API (Batch API will be used if the option is not enabled): You can transfer bulk records in a go from the source and destination org.

  4. Insert/update with Null Values: This will either insert or update record field values with null (if the value is null in source org) in destination org.

  5. Use UTF-8 file encoding for file read and write operations: Use UTF-8 as the internal representation of strings. Text is transcoded from the local encoding to UTF-8 when data is written to or read from a file. UTF-8 must be enabled if your data exclusively contains English alphabets. UTF-8 must be disabled if your data contains non-English alphabets. UTF-8 should be enabled by default in accordance with Salesforce.

Click OK to complete the feature deployment process.

You'll be redirected to the Feature Deployment Summary screen, where you can view detailed deployment reports or re-deploy the nCino objects to your Salesforce Org once again.

Last updated