Integration with Dynamics 365 / Power Platform
•Download as PPTX, PDF•
0 likes•309 views
Introduction of the possibilities to integrate with Dynamics 365 CE / PowerApps Platform. Talks about FLow, LogicApp and Azure Integration Services (Service Bus).
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Integration with Dynamics 365 / Power Platform
Similar to Integration with Dynamics 365 / Power Platform (20)
Recently uploaded
Recently uploaded (20)
Integration with Dynamics 365 / Power Platform
- 2. Integration with D365 / Power Platform INTRODUCTION OF POSSIBILITIES
- 3. Agenda • Power Platform • Workflow integrations • Flow • Logic App • Enterprise integration • Service bus / Event bus • Logic App / Azure Function • + Import and Export integrations • + Document integration
- 5. • Flow and Logic App • Flow is build on Logic App • Based on Connectors • Triggers & Actions Workflow Integration
- 6. Flow Logic App Connectors (200+) Protocol Connectors Azure Services and Power Apps Connectors Hybrid Connectors B2B, XML, EDI and AS2 Connectors SaaS Connectors
- 7. • CDS1.0 and 2.0 • Push by webhook (?) • More improvements, like attribute filters • (Current) D365 Connector vs CDS Connector • Only CDS2.0 • Pooling (?)
- 8. • Both connectors can trigger on events, but there is a third way: • Webhook from D365/CDS • HTTP Request Connector Webhook from D365/CDS Logic AppFlo w D365 / CDS webhoo k
- 9. Microsoft Flow vs Azure Logic Apps • Office workers, business users, SharePoint administrators • Run in Office365/Power Platform environment https://flow.microsoft.com • Self-service, personal productivity • 30 day limit execution • Buttons in App • Simple input supported • Approvals • Pro integrators, developers and IT pros • Run in Azure environment https://portal.azure.com • Advanced Integrations, Mission critical • 90 day limit execution • More ‘Enterprise’ Connectors
- 10. Flow – Buttons in App
- 11. Flow – Buttons in App Logic App Azure Platform Office365/ Power Platform Flow
- 12. Enable Flow in D365 ;-)
- 13. Flow – Contact form to Lead • When Contact form is submitted • Then Create Lead in D365 • And Post to Teams Contact form Flow D365 Lead Teams submits Visitor
- 14. DEMO Contact form to Lead
- 15. Flow – Account to Harvest Client • When workflow is run from selected Account • Then Ask for Approval • When Approved Create Client in Harvest • And post to Teams D365 Account Flow Harvest TeamsApproval manual starts Flow User
- 16. DEMO- Account to Harvest Client
- 17. Tangled Integration • How to manage? • What if systems are not available? • What if we lose that € 100.000 order from the website, because of this? Spotler Exact Online Website Tracking Service SMS Service ERP D365 CE
- 18. Enterprise Integration (iPaaS) • Azure Integration Services • Service Bus Event Grid • Routing Messages • Monitor and control • Transactional • Logic App (and Azure Functions) • Workflows Orchestration • Mapping • Transforming • API Management • Expose APIs • Consumer accounts • Throttling • Monetizing APIs Spotler D365 CE Exact Online Website Tracking Service SMS Service ERP iPaaS Service Bus Event Grid Logic App API ManagementAzure Function
- 19. Enterprise Integration (iPaaS) Logic App Azure Function Service Bus Event Grid D365 / CDS service endpoint webhook Logic App Azure Function Logic App Logic App ESB
- 20. Service Bus vs Event Grid • Event and Command messages • Receiver polls from queue • Advanced messaging features • FIFO, Batching/sessions • Transactions, Dead-lettering • Routing and filtering, Duplicate detection • Supports • Queues • Topics (publish/subscribe) • Relays • Event messages only • Push to receiver using webhooks • Re-active programming model • Near-real-time (faster then Service Bus) • Can handle more load • Events expires after 24 hours • Supports • Topics (publish/subscribe)
- 21. Logic Apps vs Azure Functions • Workflow triggered by an event • Extensive list of connectors(200+) • Can only run in the cloud • dependency on MS-managed connectors • Asynchronous integration and fire-and-forget messaging • Logging and tracing build-in • Code triggered by an event • Durable Functions are code- based workflows • Can be run and developed locally • Synchronous request/response calls, that execute more complex logic • Application Insights and custom
- 22. Example Enterprise Integration D365/CDS Content-based routing D365 event D365 event dead letter account account dead letter contact contact dead letter Upsert Account Convert JSON Exact Customer Queues 6 4 3 2 1 3 5 Queues
- 23. DEMO – Example Enterprise Integration
- 24. Import and Export Integrations • Data Integrator • Integrate data into CDS • Easy interface • Out-of-the-box templates • No costs • https://admin.powerplatform.microsoft.com
- 25. Import and Export Integrations • Data Export Service • Export data to Azure SQL db • Replaced by Azure Data Lake? • Azure Data Lake • o.a. SSIS • Scribe • SSIS (VM)
- 26. Document Integrations in D365 • SharePoint Online • OneDrive for Business • Microsoft Teams
- 27. DEMO – Microsoft Teams integration
- 28. Questions? Thank you! Rémy van Duijkeren E-mail / Skype for Business: remy@dynamichands.nl
- 30. Dynamics 365 Community Benefits • Participate and help build a pool of knowledge that’s accessible by members at any time! • Expand your network by engaging with peers • • • • • • Join the Dynamics 365 Community, where you can interact with your peers and Microsoft Dynamics 365 experts. You can get answers to your questions by posting questions in the forums, starting discussions, reading informative blog articles, and watching how-to videos. https://community.dynamics.com
- 31. Social www.365portal.org Twitter: @Dyn365Community Linkedin: @365-Saturday Hashtags #Amsterdam365 #365Saturday #msdyn365 Wifi: MSGUEST Pass: TBC Community.Dynamics365.com