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

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / adding rows in related...
Power Apps
Unanswered

adding rows in related entities

(0) ShareShare
ReportReport
Posted on by 13

Hi

we have a primary entity called "Accounts

this have a child entity "Orders" with relationship as 1:N

which means, one account can have multiple orders

Orders have a structure like (order id, order qty, order price) etc

 

we have created a model driven app to create accounts.

In creation form, there is a tab we added for orders. what I have observed is that, we have to create an account first and then save it, only then we are able to add orders. is it not possible to add everything in one go and save at last?

 

the issue is, we have a flow designed which gets triggered as soon as a new account record is created. so because of above issue, the flow is triggered even before orders are added to that account.

 

I have the same question (0)
  • v-xida-msft Profile Picture
    Microsoft Employee on at

    Hi @Inpriya01 ,

    Could you please share a bit more about your scenario?

    Do you want to add Orders record firstly within your Model-Driven form?

    Further, do you want to fire a flow when a new record created in your Accounts Entity along with related orders? Could you please share a screenshot about your Model-Driven form?

     

    Based on the issue that you mentioned, do you mean that you could not create Order record individually within your Model-Driven form?

     

    On your side, you could consider create a Model-Driven app based on the Orders Entity. When you create a order record in your Model-Driven form, you could select the Account LookUp field, then click "New" to create your new account record.

    Within your flow, please consider configure your flow to be fired when a new order record is added in your Orders Entity rather than Accounts Entity.

     

    Best regards,

  • David Jennaway Profile Picture
    716 on at

    In a model-driven app, you necessarily have to create the parent entity (account in your case) first, to generate the record id that is used to link the child records (order) to it.

    One workaround could be to create a field on the account, and have a workflow or Flow that runs on the order, and updates the field on the account, and have your account Flow only run on update of this field. This would mean the account Flow only runs once an order has been created

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 Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 93 Most Valuable Professional

#2
Haque Profile Picture

Haque 81

#3
Valantis Profile Picture

Valantis 49

Last 30 days Overall leaderboard