With tools such as Postman, you can easily send HTTP requests to your APIs. This technique can help test the fields that are being added to the integration message to see if they pass or fail. This helps in the efforts to test if the integration message being sent will successfully get posted in Dynamics 365.
Throughout a typical Dynamics project, various environments are setup to prevent the existing environments from being affected by the changes being pushed to an environment. This is the model most firms follow when they have mastered the release sequence in their CI/CD.
Over the course of the next 3 blog posts in my Dynamics 365 implementation series, I will go over the process and experiences my client had with implementing an ERP solution for their 50 year old, multi-billion dollar company. This first post will explain the implementation process used for this successful rollout of Dynamics 365.
Through this series I will be able to share my journey on implementing CICD process for Dynamics CRM with process workflow, POC, and tools. I am sure this will assist developers and architects in having confidence in implementing a successful CICD process for CRM.
