Showing results for 
Search instead for 
Did you mean: 
Frequent Visitor

adding rows in related entities


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.


Community Support
Community Support

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,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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

Helpful resources

PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group


Demo Extravaganza is Back!

We are excited to announce that Demo Extravaganza for 2021 has started!

MBAS on Demand

Microsoft Business Applications Summit sessions

On-demand access to all the great content presented by the product teams and community members! #MSBizAppsSummit #CommunityRocks

Power Apps June 2021

June Power Apps Community Call

Don't miss the call this month on June 16th - 8a PDT

Top Kudoed Authors
Users online (94,158)