Author: admin

Let me introduce very popular data integration’ scenario. The purpose of this presentation is an introduction a concept of CRM data integration based on Student Information System(SIS) – popular and interesting scenario. The thing is, many UK and Ireland’ universities have successfully implemented Microsoft Dynamics 365 – CRM. It is very interesting how they can take advantage of Dynamics CRM, KingswaySoft and SSIS. Based on my experience it is the best possible example to tell compelling story about CRM  data integration. Following concept keeps everything simple and really goes to the point.

1. Main points :

– Following solution was designed to provide an integration solution for passing data from/to Dynamics CRM from/to Student record System (including UCAS)

– As updates are made to the Student Information System(SIS), the updated record are written to an Intermediary Database(ID)

– Updates are periodically collected  from the Intermediary Database(ID) and written to Dynamics CRM

– As updates made to integrated records in Dynamics CRM, the updated record are written to the Intermediary Database

– Updates are periodically collected from the Intermediary Database(ID) and written to the Student Information System(SIS).

– Good data integration solution should be possible generic so config entities for data integration are implemented at CRM

– Solution covers an error handling and archiving as well

2. Daily Integration Steps
2. 1.    Collect the integration mappings configuration (config entities) from CRM

2.2.    Send Applicant data from the Intermediary Database(ID) to CRM for all applicants that are flagged as “dirty”. Dirty means that the records has been updated since it was last read (by the integration).

2.3.    Set the Applicants successfully written to CRM as not dirty.

2.4.    Read the integration last started date from CRM.

2.5.    Write the integration last started date to CRM.

2.6.    Send the following sets of data to CRM where the items are flagged as dirty (unsure?). For each Entity, set the successfully written rows as not dirty.

–    Applicants (contacts at CRM)
–    Applications (opportunities at CRM)
–    Documents
–    Form Qualification
–    Entry Qualifications
–    Clearance Checks
–    UCAS Choices
–    Communications