Refer to the following Frequently Asked Questions (FAQ) about the Conga-Dynamics 365 Data Sync connector.

Q: Where does the connector run?

A: The connector runs in Dynamics. The connector's logic retrieves data from Conga or pushes data into Conga. 

Q: What is a Sync Group and why do you need it?

A: A Sync Group specifies the group of fields that must be synced at the same frequency from the same Source-Destination combination.

Q: What objects are covered as part of the connector?

A: Any object from Dynamics 365 or Conga can be used for syncing.

Q: Can I configure objects or does the effort require assistance from Professional Services?

A: You can configure any object in Dynamics 365 or Conga. Follow the standard object creation steps in the respective platform. Data Sync does not participate in this step.

Q: Can data be bi-directionally synced between two systems?

A: Yes and no. Data sync is bi-directional for more than one object, but each object can only be synced in a single direction. For example, you can set up a sync group to sync the Agreement object and its fields from Conga to Dynamics, but you cannot at the same time set up another sync group to sync the Agreement object and its fields from Dynamics to Conga. 

Q: Can the connector sync data in real time?

A: No, the connector currently supports scheduled sync only based on a pre-defined interval.

Q: There is no "Money" type in Conga, it is "Currency" instead.

A: The data sync admin is responsible to set up field types to map equivalent fields.

Q: Is there a character limit for the Mapping Name field?

A: Yes. The limit is 100 characters.

Q: Can MultiSelect fields be synced?

A: The MultiSelect field/picklist data type is not currently supported.

Q: How can I sync lookups to an object that was part of the initial load?

A: The Id field must contain data as part of the initial load. The Id field at the destination should match the source record Id. For example, if 50,000 agreements are loaded in Conga and Dynamics and the sync is from Conga to Dynamics, then each agreement's record Id field in Dynamics must have the same value as the corresponding Conga Id.

Q: Can the sync frequency be set for each entity?

A: The data sync frequency is set for each sync group, which consists of one or more entities.

Q: Which CRUD operations are supported by Data Sync?

A: All operations (insert, update, upsert, and delete) are supported.

Q: Is there an option in the connector through which a user can control the specific operations (insert, update, delete, and so on) to be executed on sync?

A: This feature is not currently supported.

Q: What level of support is provided for transformation?

A: The connector does not support transformation of data and there are no plans to support it. The data is synced as is from the source to destination. Use of a middleware or ETL is suggested for supporting transformations.

Q: Do we have the option to configure customer External Id fields?

A: The External Id can be a custom field. However, it always stores the source record Id at the destination.

Q: What is the shortest sync interval supported? Would it be possible to set it for 1 - 2 minutes for some entities?

A: The minimum sync interval is 3 minutes. Refer to Setting Up a Scheduler for Data Sync for details on creating sync processes when the interval is less than one hour.

Q: How is data sync executed when different objects in a sync group have differing values for "Last Sync Time?"

A: Each object is synced based on the time updated in the "Last Sync Time" field of that particular object.

Q: What are the values supported by the "Sync Status" field under a sync group?

A: The following are valid values for the Sync Status field:

  • Success: Shown when the last sync run was successful.
  • Error: Shown when the last sync run failed.
  • Running: Shown when a sync run is in-progress.
  • Paused: Shown when a sync has been paused and will resume at the next scheduled time.
  • PartialSuccess: Shown when some, but not all records sync successfully.

Q: Can this process be executed on demand?

A: This is not planned. The punch-out flow accomplishes that.

Q: Is there a time maximum for sync run execution?

A: Yes, the sync run maximum is 2 minutes. If a sync run takes longer to process, the connector pauses and continues the sync at the next scheduled sync run. 

Q: Is this only for Contract Lifecycle Management (CLM) or can it also be used for CPQ?

A: Data Sync can be used for any Conga application.

Q: Is there an API to start sync process?

A: This is being investigated for a future release.

Q: If a record fails and the issues is corrected, is the record synced again?

A: Yes, after the record has been updated at the source it is synced at the next scheduled run.

Q: Suppose an object "O1" is synced from Dynamics to Conga and a lookup with "O2" to "O1" relationship exists in Conga. When "O2" is synced from Conga to Dynamics, how does Dynamics know that "O2" needs a lookup to the appropriate object?

A: The lookup relationship is established using the Id–so the object "O2" lookup field value points to the lookup record Id.

Q: Are performance numbers and governors limit published anywhere?

A: Yes. Refer to Performance Benchmarks.

Q: Does the customer need to buy any additional licenses to support the data sync process on Dynamics?

A: This product is included for all Conga customers that use Conga with Dynamics 365. 

Q: Why would a customer choose this product over a standard middleware?

A: While the best way to do this would be through Middleware, some customers do not have it or it adds a load on IT that they do not want to manage.

Q: So Conga will not provide any out-of-the-box basic sync? Every customer will build their own?

A: The ability to create mappings is self-service and takes about an hour to do by a trained Business Analyst. 

Q: Does the sync work for on-premise Dynamics?

A: No. The connector is not currently supported for on-premise Dynamics.