web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Dataverse: Dynamically Retrieve Form Field Metadata for OData Consumption

(2) ShareShare
ReportReport
Posted on by 5

Dear Dynamics Team,

Good morning.

We are working with Microsoft Dynamics 365 / Power Apps (Dataverse) model-driven apps. We have Dataverse tables with model-driven forms where fields (columns) are configured dynamically by administrators (for example, adding new columns and placing them on a form).

Our requirement is to consume this data in a custom mobile application using the Dataverse OData (Web API). We would like to dynamically retrieve the configured field (column) names and metadata so that we can:

  • Construct the OData service URL dynamically at runtime

  • Display the fields and their corresponding data in the mobile application

  • Automatically handle newly added fields without requiring any additional development or code changes in the mobile app

Specifically, we would like your guidance on the following:

  1. Is it possible to retrieve the form-level field configuration (i.e., fields placed on a specific model-driven form) via Dataverse metadata APIs or OData/Web API?

  2. If so, what is the recommended or supported approach to read form metadata and associated table columns dynamically?

  3. Are there any best practices or limitations when using Dataverse metadata and OData for this use case?

Your clarification on the supported approach would help us design a scalable and future-proof integration.

Thank you for your support.

image.png
I have the same question (0)
  • Suggested answer
    Olufemi 7 Profile Picture
    28 on at
    Hello @SP-31010500-0

    Dataverse supports dynamic field discovery for external apps via the Dataverse Web API metadata for tables and columns, while form layouts are stored in a system table and parsing XML is required if needed, though not recommended, as forms are a presentation-layer artifact.

    Microsoft Docs: 
    Use the Web API with table definitions
    System Form (SystemForm) table/entity reference (Dataverse) — Microsoft Learn




     
  • 11manish Profile Picture
    365 on at
    Yes, partially
    But not in the way most people expect
    Form layout is not designed to be a UI contract for external apps
     
    Can You Retrieve Form-Level Field Configuration?
     
    Yes — but not via normal OData entity queries.
    Model-driven form metadata is stored in the SystemForm table.
     
    Relevant table:
    • systemforms
    Best practices
    • Cache metadata
    • Avoid XML dependency
    • Use configuration table for mobile layout
    • Handle security dynamically
    • Avoid assuming form layout equals data contract

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
11manish Profile Picture

11manish 174

#2
ManoVerse Profile Picture

ManoVerse 58 Super User 2026 Season 1

#3
Niki Patel Profile Picture

Niki Patel 42

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans