Technical Consulting Manager
Since D365 is a SaaS application, you won't have direct database access. Learn how to work within the app framework and use APIs to connect to the data, as well as how to leverage middleware. In this video, we'll address the integrations lifecycle, including analysis, building and deployments, testing, and overall strategy considerations.
Integration Implications Takeaways
Direct database access is no longer allowed. You'll need to work within the apps framework and use APIs to connect to the data. Use middleware for API management and orchestration. You’ll also want to consider taking advantage of cloud tools such as Azure Blob or Azure Service Bus.
Analyze the systems you're integrating with. What are they? Why do you need integration? What tech do they support? How much can you customize them?
Once you've designed the integrations, you'll need to build and deploy. These steps include distilling individual endpoints and deploying test environments.
Integrations require a series of tests, including functionality testing under different conditions in all environments. Test for performance including peak load and volume. You'll want to benchmark these processes and coordinate with SaaS applications test. You automate testing using tools like Postman or SoupUI and D365 Task Automation framework to prevent regression test.
You may not require as many integrations with D365. There are new tools and features as well as first-party integrations like D365 Field Services or D365 Customer Engagement. Look to minimize your team's efforts by leveraging Microsoft and partner integration templates.
More D365 Upgrade Resources from Blue Horseshoe
Upgrading to D365: Timelines
Upgrading to D365: Digital Transformation
Upgrading to D365: Continuous Updates Recommendations
Upgrading to D365: Data Conversion Recommendations
Upgrading to D365: Code Upgrade Recommendations
Upgrading to D365: Development Implications
Upgrading to D365: Continuous Updates Implications