Deployment via Template using Salesforce Org
Last updated
Last updated
This section is all about deploying the nCino data via the salesforce org dataset.
Hover your mouse over the nCino module and click on the Deployment History option.
Click on the Feature Deployment button.
On the next screen, give the process a name and a brief description.
In the SOURCE section, select Deployment From as Template using Salesforce Org.
Select the template Feature Type i.e, Standard or Community Template.
Select your Template and its Version of it.
Select your Source Salesforce Org.
The object configuration section will render the selected objects and apply filters and mappings based on your template selection.
Choose your Destination Environment. It can be your target salesforce org or commit to your version control branch.
To deploy into a salesforce org, select the Deploy To checkbox and choose your Destination Org. To commit to a branch, select the Commit To box, enter your Repository/Branch details, and comment (if any).
Important Note: For commits, the features will get committed to the default location in your version control branch. By default, the location is set to the dataset.
There are various options that you can configure to your objects before you proceed with deployment or commit:
Applied Mappings
Sorting (only if the 'Commit to' checkbox is selected)
Applied Filters
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):
Since the source for Deployment via Template or Version Control is a CSV file rather than a Salesforce Org, all fields, regardless of the External ID supported, will be fetched and displayed in the Source column. However, the relevant fields will be shown under the Destination column since the target org is a salesforce org.
AutoRABIT External ID fields are not supported for the Upsert operation.
This new feature allows you to sort fields for nCino objects while committing. Based on the sorting order set, the record order in the JSON files will get fetched. The users will be provided a default sorting order that can be changed. XXXXX_lookupkey__c is the most preferred field for sorting, and that would be the default field. If this field is not present, the Name for custom settings and Id for non-custom settings would be selected.
For the objects with sorting fields opted, the sorting icon gets changed.
Such filters will be displayed here if any filter is applied to the objects. You can edit the already applied filter (if required) using Edit Filter.
Based on your destination selection, you will have different deployment buttons to choose from:
Create Dataset: Create a dataset from your Salesforce Org
Create Dataset & Deploy: Create a dataset and deploy it to your Salesforce Org
Create Dataset & Commit: Create a dataset and commit to a Version Control Branch
Create Dataset Commit & Deploy: Create a dataset and proceed for both commit and deployment.
For deploying to the destination org, you will find the list of deployment criteria you can opt for before proceeding.
Deployment Filters
Disable Workflow Rules: This option will deactivate the workflow rules associated with objects part of the deployment
Disable Validation Rules: This option will deactivate the validation rules associated with objects part of the deployment
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
Insert/update with Null Values: This will either insert or update record field values with null in the destination org (if the value is null in the source org)
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 page, where you can view detailed deployment reports or re-deploy the nCino objects to your Salesforce Org/Version Control once again.
