In between any two applications, there might be another application or service that translates information from one database to the next, from one application to the next, from one method to the next, from one service to the next, or from one user interface to the next. As we integrate, extend, and expand Microsoft Dynamics CRM into environments where other software applications already reside and where integration is needed, we are faced with differences between designs and database structure.
How should we approach this situation? There is an option to write custom software to tie multiple applications together, but this can be time-consuming and error-prone, and it can require a long-term investment in updates and upgrades. ...
No credit card required