Power Platform Solution Architecture: Introduction to data

So friends, in this next part of my series on solution architecture for the Power Platform, I’ll be focusing on data and the element of solution design that focuses on data architecture when working with the Power Platform and Dataverse. In this post, we’ll… READ MORE [https://lewisdoes.dev/blog
close up photo of gray laptop
Photo by Lukas on Pexels.com
In: Low Code Lewis Content 🚀

So friends, in this next part of my series on solution architecture for the Power Platform, I’ll be focusing on data and the element of solution design that focuses on data architecture when working with the Power Platform and Dataverse.

In this post, we’ll look at an introduction to what data modelling is (the thing we will do as architects during the design phase), what our role is, and how we come to a best solution.

What is data modelling?

Data modelling is the art of organizing and structuring data to fit the specific needs and requirements of a business or organization. It’s like developing a blueprint that outlines how data will be stored, accessed, and manipulated within a system or database. By defining relationships, constraints, and rules, data modelling ensures that information is managed effectively and accurately. It’s essentially like being an architect for data, constructing the framework that supports the entire infrastructure.

Data models effectively show the relationship types between tables and give a high-level visual representation of what our data structure or ‘schema’ looks like under the data we actually store in that structure / schema.

When working with Power Platform, it’s crucial we get this step right as it will affect everything right up to custom logic implemented and app design, especially when working with model-driven apps.

What should you be doing?

So friends… as solution architects what is your role… Consider some of these points…

  • Own the process involved in designing a high-level data design / architecture for the project
  • Ensure that the data model designed can be extended collaboratively
  • Constantly own the process of reviewing and updating a design for the data model as it evolves as new features are designed or requirements understood in more detail
  • Ensure the design of the data model fits the capabilities of the Power Platform and takes the common data model into account

What will help?

So if you’re new to data modelling, the best thing you can probably do is check out a bunch of different use cases and begin trying to think about how the data for those could be stored. If you’ve worked as a developer on projects before try to look back at those and see how data is structured in those implementations and match those up to the use cases and business requirements achieved to get an idea of how to design a data model.

What’s coming up?

So do you remember I mentioned that point about you needing to make sure you’ve considered the common data model when working with Dataverse. Well friends, in my next post we’ll look at just that and what to focus on in this area when architecting data models for the Power Platform! 🚀

Written by
Lewis Baybutt
Microsoft Business Applications MVP • Power Platform Consultant • Blogger • Community Contributor • #CommunityRocks • #SharingIsCaring
Great! You’ve successfully signed up.
Welcome back! You've successfully signed in.
You've successfully subscribed to LewisDoesDev.
Your link has expired.
Success! Check your email for magic link to sign-in.
Success! Your billing info has been updated.
Your billing was not updated.