Introduction

RaiseNow builds on top of the standard D365 functionalities for detecting and avoiding creation of duplicates. This means by defining standard deduplication rules in D365, these rules are automatically leveraged by RaiseNow when interacting with D365 in order to avoid creating duplicate entities. Please refer to the Microsoft documentation for more details. 

This mechanism is supported for interactions with the following entities

• Account
• Contact

Before creating a new account or contact, RaiseNow will query D365 with the information available. If D365 reports a detected duplicate, RaiseNow will continue the process with the provided record instead of creating a new record. 

Note: D365 may return multiple records. In this case RaiseNow will always use the first returned record. 

In addition, depending on the relevant entity, RaiseNow will set the following properties on the commitment created in the process:

• Account: rnw_accountduplicatereportedbyd365
• Contact: rnw_contactduplicatereportedbyd365

The corresponding property will be set 'true' if a duplicate for the entity type is detected. In addition, RaiseNow will set the following fields on the created commitment according to the entity type of the duplicate detected: 

• Account: rnw_eventnotificationaccountdetails
• Contact: rnw_eventnotificationcontactdetails

The field will contain a json with the parameters originally sent in the submitted donation. For example:

{"salutation":"mr","firstname":"Rio","lastname":"Heiser","email":"doe+rheiser@raisenow.com","email_permission":true,"language":"en","supporter_uuid":"a8c55af82b3548c3b2953b551e2ba9cddc2e1d4f","street":"Hardturmstrasse 101","postal_code":"8005","city":"Z\u00fcrich","country":"CH"}

This information is provided to allow you to implement your own custom process for updating entities in D365 according to the rules of your organization.