Submit a Ticket My Tickets
Login  Sign up

Object Merge Settings

Table of Contents

Background Information
Supported Entities/Objects
Related Articles


  • Coursedog integrations rely on a Default Source of Truth (DSOT) to determine how to resolve conflicts. This is generally configured at the entity level (Admin > Merge Settings) when integrating our products. 

  • For example, Rooms often utilize an “Always Institution” DSOT because this is data that should flow from the institution's SIS to Coursedog and little-to-no changes should occur in Coursedog. 

  • However, individual records can have different DSOT settings applied to protect data or ensure updates. You can do that in Coursedog by using the “Object Merge Settings” field in Academic and Events Scheduling as well as Curriculum Management.

Background Information

Review the following articles for more information on how merges and conflict resolution work in Coursedog:

Supported Entities/Objects

The prebuilt Object Merge Settings field is available in the following applications and templates.


Entities/Object Templates

Academic Scheduling

Section, Instructor, Room



Curriculum Management 

Programs, Courses



  • As mentioned above, the Coursedog implementation team and your institution's administrators configure DSOT for each object type (“Entity”) through the Admin > Merge Settings panel.

  • Overriding this setting for an individual record or object requires adding the “Object Merge Settings” prebuilt question to that entity’s template so that it can be adjusted for individual records. 

Adding Prebuilt Question to Template

Step 1: 

  • To enable this feature, drag and drop the Object Merge Settings prebuilt field to the relevant template.

  • Refer to this article for general instructions regarding adding fields to templates.

Step 2: 

  • Once placed in your template, click into the field to configure its Questions Settings. 

  • We recommend leaving the default blank so that it uses the value defined at the entity type and merge settings. 

  • This field may require additional training for users to fully understand its use. To avoid merge errors, we recommend restricting access by role to administrators or registrars unless use cases require general access. 


  • The “Object Merge Settings” field should always be set to "Always Coursedog" in the corresponding entity type merge settings field exceptions; otherwise, it could be erased in a merge. This can be configured by an Admin at Admin > Merge Settings. 

  • If “Object Merge Settings” isn’t available to select from the list of fields, enter a custom field exception for the path objectMergeSettings (shown below).

  • Any field exceptions will still apply as defined in merge settings. So if for rooms the DSOT is "Always Institution" and there is a field exception for capacity to "Resolve as Institution", even if a particular room has Object Merge Setting = "Always Coursedog" the capacity for that room may be updated by the integration.

  • If the Object Merge Settings field is not on the form, or on the form and not set, there is no change to behavior: The entity will just take default merge settings from the entity type, as defined at Admin > Merge Settings. 

Related Articles

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.