Create a Feature Migration Template with Predefined nCino Objects


This article deals with the step-by-step procedure to create a standard/community template by picking a feature with nCino predefined objects.


  1. Hover your mouse over the nCino module and click on the option: Feature Management.

  1. Click on New Feature Migration Template button.

  1. Choose one of the features from the list. For example, select the Spreads Schedule Template tile to include the Spreads Schedules feature predefined objects in a template.

  1. You'll be navigated to Record Based Configuration section, where you will find three tabs that need to fill in to proceed ahead:

    • Metadata Configuration

    • Record Configuration and

    • Preview and Save

Metadata Configuration

To create a feature migration template, you must provide basic details on this tab.

Under Feature Details section, fill in the below details:

  1. Name: Provide a feature migration template name.

  2. Associated Partner: The default associate partner would be nCino, which you can change if necessary.

  3. Version: Enter the version number here. If you're creating the feature template for the first time, it is recommended to keep the version number as 1.0.

Under the Salesforce Org Details section, do the following:

  1. Choose your Salesforce Org.

  2. Click Fetch Objects to retrieve all available objects in the selected source org. Predefined objects will be auto chosen based on your selected feature. By default, only nCino objects available in the source org will get auto-populated. To view all the objects available, click on Show All objects.

  1. Click Next to go to the Record Configuration tab.

Record Configuration

This tab is where you apply filters for the entry objects. Also, on the left side of the screen, you can see the list of items that are segregated into:

  1. Selected List: This will include a list of all objects that are part of your selected template and objects that you have chosen to add later.

  2. Related List: This section will only be displayed in the Attachment Object for your migration template feature is included.

  3. Required List: This contains mandatory objects, and you cannot exclude them,

  4. Excluded List: This section lists non-required data objects you could permanently exclude while creating a template so that the template does not contain data object information. Depending on the selected template, some objects are auto-selected, and you can deselect them.

Based on the object's relationship, the AutoRABIT application will segregate the object sets, and applying a filter on each bucket is mandatory. By default, AutoRABIT will denote an object in a bucket as an entry point, which can be applied filter. This is not mandatory, but as a best practice, AutoRABIT recommends applying filters to the entry point object rather than any other object.

The entry object is selected by default, and the user can apply a filter. The entry object is denoted by “E”.

Applying the Filters

Apply the filter(s) using the steps as shown below:

Click Add. The filter query gets added and gets displayed in the filter box. You can edit the query if any modification is required. Nevertheless, multiple queries can be added based on your requirement. Validate your query to see if the query entered is stable or not. Additionally, you'll be able to view several records that will get fetched.

Important Note:

  1. All records that get fetched will be in order by "ASC nFORCE__lookupKey__c." Nevertheless, if "nFORCE__lookupKey__c" is unavailable, then using order by "ASC Id," the records will be fetched.

  2. For the Attachment object, the filter cannot be applied.

You can also use the Query Editor to execute a SOQL query on the selected source org. Results are displayed in a Query Results grid.

Similar steps are to be followed for objects in other buckets as well. Once done, click Next to proceed to the Preview and Save screen.

Important Note:

  1. If your nCino objects include an Attachment object, the users must confirm whether they want to fetch the Attachment dataset.

  2. Please check the number of attachments pulled for the job once the attachment object is selected as part of the data deployment. For each API call, Salesforce returns at least one and a maximum of five attachments based on the size of the attachments. For more attachments, more APIs call will get triggered, which may result in the APIs limit exceeding and the application to throw an error.

Preview and Save

This is the summary page for the feature migration template you're about to create. You can view the features details, and filters you have applied for the last time before the template is created. Any change log information that needs to be added can be mentioned in the Change Log box.

Important Note:Related List section will display only if the Attachment object is a part of the Feature Migration Template.

Click Save, and you will be redirected to the Feature Migration Summary screen, where you can track your template recently created.

Last updated