Book Image

Microsoft Power Platform Solution Architect's Handbook

By : Hugo Herrera
4.5 (2)
Book Image

Microsoft Power Platform Solution Architect's Handbook

4.5 (2)
By: Hugo Herrera

Overview of this book

If you’ve been looking for a way to unlock the potential of Microsoft Power Platform and take your career as a solution architect to the next level, then look no further—this practical guide covers it all. Microsoft Power Platform Solution Architect’s Handbook will equip you with everything you need to build flexible and cost-effective end-to-end solutions. Its comprehensive coverage ranges from best practices surrounding fit-gap analysis, leading design processes, and navigating existing systems to application lifecycle management with Microsoft Azure DevOps, security compliance monitoring, and third-party API integration. The book takes a hands-on approach by guiding you through a fictional case study throughout the book, allowing you to apply what you learn as you learn it. At the end of the handbook, you’ll discover a set of mock tests for you to embed your progress and prepare for PL-600 Microsoft certification. Whether you want to learn how to work with Power Platform or want to take your skills from the intermediate to advanced level, this book will help you achieve that and ensure that you’re able to add value to your organization as an expert solution architect.
Table of Contents (23 chapters)
1
Part 1: Introduction
4
Part 2: Requirements Analysis, Solution Envisioning, and the Implementation Roadmap
10
Part 3: Architecting the Power Platform Solution
15
Part 4: The Build – Implementing Solid Power Platform Solutions
20
Part 5: Power Platform Solution Architect Certification Prep

Resolving integration conflicts

Solution architects review the designs and implementation of Power Platform integrations to identify areas where they may be a conflict between them or other business processes. The actions and domain for each integration are reviewed individually and in combination with different integrations to identify potential clashes.

A typical example of an integration conflict is enriching contact data from two different sources:

  • One integration may be responsible for updating a contact’s address and contact details.
  • A second integration may also update contact details, overwriting the first integration’s data.

The result is a Dataverse contact with data in an inconsistent state.

The following steps will help you identify and resolve integration conflicts:

  • Review the integration designs to identify which interfaces interact with the affected data item.
  • Review the actual implementation, scanning for Power Automate...