Hi Everyone,
Customer have a requirement wherein the CRM 2015 On Premise will be integrated with GIS system. We have discussed several options on which approach (within Microsoft Best Practice) should be to taken. Their GIS application has sort of limitation that it only accepts kind of objects in SQL to fully use its functionality (tagging, symbolizing, etc..). The application is joining their table and the attributes it is retrieving from the CRM Database on the fly.
- GIS application will be querying (read only) directly into tables of CRM Database.
1.1. I'm well aware that querying directly into tables of CRM Database is not supported as it may result with a lot of problem (void warranty, data issues., etc.).
- Create dump database where CRM records will be dumped over and GIS application will be querying to the dump database.
2.1. We will create a plugin/console app wherein it retrieves data from CRM and dump the record over to the dump database.
- GIS application will be querying from CRM’s web service.
3.1. As I have discussed above, the GIS application only accepts kind of objects in SQL to fully use its functionality like tagging, symbolizing etc., which the customer really needs.
- GIS will create an application wherein it translates every attributes it needs into a SQL object
- GIS application will be querying from the View of the SQL to read attributes and its values.
Based on what we have discussed; it looks like we are going option #5. What I would like to know is, is that still the same with querying into tables of CRM Database which is an unsupported way or that is already a supported way? If yes, is there a white paper that discussed about this? Can you also please help me what the architectural design will be?