powerobjects: Dynamics 365 Integration: Testing Best Practices
Testing the data flow within two separate systems to ensure accuracy and consistency of data is called integration testing. Microsoft Dynamics 365 can be integrated with other systems. First, let’s take a look at a few ways we can leverage integrations and some examples of why we might use one of these integrations. Then we’ll take a look at how test that data flow.
Integration between Dynamics 365 and an External Database
This is very common scenario where CRM is integrated with another application’s database. For example, Contact, Accounts, or System User data is pulled from Feed-Store and stored locally in CRM for further business processes. Data is pulled from external systems using SQL jobs or by Web service calls. The frequency to pull data depends on how often the data is been modified in the source system.
Integration between Dynamics 365 and a Web Form
Web Forms enable external individuals (non-Dynamics 365 users) to submit a request to Dynamics 365. For example, a customer logs into an external system and inquires about a product and then a lead is created in Dynamics 365.
Integration between Dynamics 365 and a Portal
The integration of Dynamics 365 with a Portal allows the users of the portal to submit requests into Dynamics 365. For example, a customer logs into a portal and submits a request for support for an installation that they bought – then a case is created in Dynamics 365.
Web-Service is consumed by Dynamics 365
The source system may expose a web-service such that Dynamics 365 retrieves the data from their system so that the business rules are honored. For example, the products data is stored in an external system but is consumed by Dynamics 365 for creation of Quotes and Orders to complete the sales process in Dynamics 365.
Web-service is exposed by Dynamics 365 for External Applications
Sometimes the external system needs data from Dynamics 365 for further processing in their system. For example, upon qualifying a lead, an Opportunity, Account, and Contact is created. Dynamics 365 exposes the unique ID created for the Opportunity to an external system.
These tests scenarios cover validating Dynamics 365 interactions with any of the above mentioned external systems.
Keeping reading our blog for more helpful Dynamics 365 tips and best practices!
Happy Dynamics 365’ing!
Расскажите о новых и интересных блогах по Microsoft Dynamics, напишите личное сообщение администратору.
|powerobjects: How to Integrate Power BI with Dynamics 365 for Finance and Operations||Blog bot||Dynamics CRM: Blogs||0||26.06.2018 01:23|
|powerobjects: Authentication to Dynamics 365 using Azure Apps||Blog bot||Dynamics CRM: Blogs||0||18.05.2018 21:17|
|powerobjects: Raising Dynamics 365 Awareness through Microsoft Stream||Blog bot||Dynamics CRM: Blogs||0||27.03.2018 02:35|
|powerobjects: Visualizing Data in Dynamics 365||Blog bot||Dynamics CRM: Blogs||0||03.01.2018 05:45|
|CRM DE LA CREME! Configuring Microsoft Dynamics CRM 4.0 for Internet-facing deployment||Blog bot||Dynamics CRM: Blogs||0||18.08.2009 11:05|
|Опции темы||Поиск в этой теме|