Unanswered

What are the considerations for meta data driven architecture?

(0) Share

Report

Posted on by nilanjan

I understand the general idea of the power platforms meta data.

How do you take the meta data into account when creating applications? Can you point me to some examples? Are there any links for understanding the implications of a meta driven architecture?

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

v-xida-msft Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi @nilanjenator ,

Do you want to create a Model-Driven app in your PowerApps?

Actually, the Model-Driven App in PowerApps is migrated from Dynamics 365 CRM Form App, and it use the Common Data Service Entities as the only data source. Model-driven design uses a metadata-driven architecture so that designers can customize the application without writing code. Metadata means “data about data” and it defines the structure of the data stored in the system.

The Model-Driven design is provided a UI experience to design a app without writing any code. So you just need to focus yourself on creating CDS Entity to store the data, and create some Forms, Views, Dashboards, ... related to this Entity, which would be used in your Model-Driven app later.

More details about Model-Driven app and Standard alone canvas app, please check the following video:

https://www.youtube.com/watch?v=WMlO8ngbcos

https://www.youtube.com/watch?v=3yN0-qBL8nA

More details about Model-Driven sample app, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/overview-model-driven-samples

Components in Model-Driven app, please check the following article:

https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/model-driven-app-components

Best regards,

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on at

Like (1)

Report
Copy link

Link copied!

The reason that power platform and common data service are metadata driven is because you are dealing with entities that are abstracts of the underlying tables and you have metadata driving the configuration.

“
The web application or different clients people use to interact with the data in your environment depend on the entity metadata and adapt as the entity metadata changes. But these clients also depend on other data to control what visual elements to display, any custom logic to apply, and how to apply security. This system data is also stored within entities but the entities themselves are not available for customization.”
https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/create-edit-metadata#metadata-used-with-customization

Was this reply helpful? Yes No
Joel CustomerEffective 3,224 on at

Like (0)

Report
Copy link

Link copied!

The way you take metadata into account is using solutions so the metadata and customization built can be moved via xml file. Also tools like the xrm toolbox let you have increased control over metadata for things like user settings that impact your users’ experience

note with canvas apps you can connect to any number of data sources, some of which are more metadata driven than others

Was this reply helpful? Yes No
nilanjan 6 on at

Like (0)

Report
Copy link

Link copied!

@jlindstrom @v-xida-msft I posted another question to explain more what I am looking for: https://powerusers.microsoft.com/t5/Common-Data-Service-for-Apps/How-do-you-handle-navigational-properties-and-optionsets-during/m-p/609100#M5993

Was this reply helpful? Yes No
v-xida-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @nilanjenator ,

If you have opened another thread to describe your issue. Please consider go ahead to click "Accept as Solution" to close this thread. Then we could help you in your new thread.

Best regards,

Was this reply helpful? Yes No