Load to Dynamics Action Type
This article helps the admins configure the Load to Dynamics Action type using Horizon Rules in the Rules Engine.
Overview
Admins can configure the Load to Dynamics Action to sync data from Gainsight to Dynamics. Rules Engine provides the ability to prepare the dataset from various standard and custom objects of Gainsight, and the Load to Dynamics action type sends the data to the tables in Dynamics.
Gainsight recommends reading the configuration of the Rules Details, Data Setup, and Schedule steps before reading this article. For more information, refer to the Create New Rule section of the Rules Engine Horizon Experience Overview article.
Limitations:
-
Dynamics integration is API based. Hence it will take longer than other external systems which have bulk ways to load data.
-
The processing time for each Dynamics instance might wary depending upon the set up and resources available at the time of request.
Note: Each record consumes one API call for the ingestion, hence for 10k records 10k API calls are used.
Configure Load to Dynamics Action Type
To configure the Load to Dynamics Action type:
- In the Action Setup step, click the Add Action icon. The Add Criteria slide-out panel appears.
- (Optional) Click Add Criteria to define filter criteria for the dataset.
- Click Skip This Step to navigate to the Add Actions step.
- From the Create Action drop-down list, select the Load to Dynamics Action type.
- In the Load to Dynamics section, provide the following details:
- From the Connectors drop-down list, select the Dynamics connection.
Note: The Dynamics Connection must be authenticated on the Connectors 2.0 page.
- From the Object Name drop-down list, select the tables to which you want to transfer the data.
- From the Operation drop-down list, select one of the following:
- Upsert: Updates the records that match with the given upsert key. If no records match, a new record is created.
Note: If a target object has 10 fields, and the data to be loaded has only six fields then in:- Update operation the six fields get updated and the remaining fields remain unchanged.
- Update operation the six fields get updated and the remaining fields remain unchanged.
- Insert: Inserts new data from the source fields into the target fields.
Note: If a target object has 10 fields, and the data to be loaded has only six fields then in:- Insert operation, the remaining four fields will have null values.
- Insert operation, the remaining four fields will have null values.
- Upsert: Updates the records that match with the given upsert key. If no records match, a new record is created.
- (Optional) Description: Enter a description for the rule action.
- In the Field Mapping, map each Source Field to its respective Target Field.
- (Optional) Add a Default Value.
Note: This value is loaded in the target field in case the source field value is invalid or not available. - (Optional) From the Add Fields dropdown, select Custom Field. A custom value can be mapped to the target field in the Dynamics object.
- From the Connectors drop-down list, select the Dynamics connection.
- Click Save Actions. The Load to Dynamics Action Type is saved successfully.
Schedule the Rule
The rule that is ready with the dataset and required action setup can be scheduled as per time-based and Event-Based schedules. You can schedule the execution of an individual rule in chronological order.
For more information on how to schedule a rule, refer to the Schedule and Execute Rules article.