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

Optimal reference and configuration data modeling strategies

Power Platform applications often use lists of reference data. A list of countries or a lookup table listing all the functions within an organization are typical examples. Users select from these lists of reference data to categorize and process records.

Modeling reference data

When planning the structure of reference data within Power Platform applications, solution architects consider the benefits versus the additional complexity adding new tables brings to the solution:

  • Create a table instead of a Choice or Choices column if there is a chance the list may need to be enhanced with related information (for example, currencies related to a list of countries).
  • Use standard built-in tables if the use case closely matches the table’s function.
  • Use Azure DevOps Build Tools where possible to promote reference data.
  • Maintain the unique IDs of reference data to keep referential integrity and help...