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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Model Driven App (MDA)...
Power Apps
Answered

Model Driven App (MDA) - Linking to data flows mapped tables with hierarchy

(3) ShareShare
ReportReport
Posted on by 44
I have a situation where I have a Model driven App that connects to our ERP data. 
 
I have set up Dataflows that map to tables within my application that are Periodically updated with the ERP Data (ie Live-ish data). The only way to change the data is through the ERP and passes the updates through the dataflow. The dataflows are then mapped to MDA tables for use.  The question is some of the linking that goes along with its use.  I would like to have my connector table that uses the Project number that fully brings the project data into the application for viewing.  
 
DF(s) = > mapped Solution tables  
  • Header Project (Project # is Key Field)
    • Child Financials (Project is Key reference Field) 1;N
    • Sub-Child WBS (Project Is Key Reference Field) 1;N
 
Where I am having a problem is the connection, I can easily connect to the header file. The problems are the child references of the periodically updated external data.  How could I do the single selection of the Project number so the lower levels automatically connect to the children table items.
 
  • Linking Table  connects to Header Project (Project # is the Key Field)
    • Child Financials (Project# is Key reference Field) 1;N
    • Sub-Child WBS (Project# Is Key Reference Field) 1;N
Any guidance or ideas would be helpful 
I have the same question (0)
  • Suggested answer
    MParikh Profile Picture
    322 Super User 2025 Season 2 on at

    If you want true Dataverse relationships, you can use a post-processing flow:

    Step 1: Sync ERP data using Dataflow to raw staging tables
    • Let’s say:
      • ERP_Project_Staging
      • ERP_Financials_Staging
      • ERP_WBS_Staging
    Step 2: Use a Power Automate flow to:
    • Loop through each row in staging (Financials/WBS)
    • Use Project# to LookUp the actual Project record in Header Project
    • Update Financials/WBS records to set a lookup to the Project table
    For each WBS record
    → Lookup Project in Header Table where Project# matches
    → If found, update WBS record with Lookup(ProjectId)
     Benefit: This creates real 1:N relationships in Dataverse
    You can now use subgrids and related views in MDA natively
     
  • Verified answer
    Erikpgh1 Profile Picture
    44 on at

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 765 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 343 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 272

Last 30 days Overall leaderboard