Subgrid - How to import data to a sub-grid in Model Driven App

(0) Share

Report

Posted on by ctrl_kudorje

173

How to import multiple rows of data to a sub-grid in Model Driven App and still keep the relationship after import?

Allow me to expand, i have two tables that i would like to move to dataverse, Invoices (header) and Invoice_lines (child). They are linked via invoice_id field. I want to create a model driven app where a sub-grid (Editable), wherein I can edit the ones that already exist, and/or add new lines and add them to the Invoice_lines table while it maintains a relationship.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (5)

Answers (0)

Michael E. Gernaey 53,969 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi @ctrl_kudorje

the question is not clear as you don’t import data into a grid. You import data into a table and if an Entity has relationships and if you add a grid, it will show them.

Can you please explain the data you are importing and the relationship it has with existing data.

or are you importing data for the parent and the child?

Was this reply helpful? Yes No
Suggested answer

Fubar 8,487 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

You may need to be more clear - a subgrid is just a control that shows records linked to the current record by either a one-to-many or a many-to-many relationship (but you can configure it to show all data in a table also).

How you may import data is different for a one-to-many vs a many-to-many. For a one-to-many your import file must include a column that either has the GUID of the parent record or some other unique identifier on the parent record. You then use standard data import to import the records, you may need to update the Mappings depending on where your data is coming from.

https://learn.microsoft.com/en-us/power-apps/user/import-data

many-to-many is more complicated, so will hold off describing it unless it is confirmed that is what you need

Was this reply helpful? Yes No
ctrl_kudorje 173 on at

Like (0)

Report
Copy link

Link copied!

Allow me to expand, i have two tables that i would like to move to dataverse, Invoices (header) and Invoice_lines (child). They are linked via invoice_id field. I want to create a model driven app where a sub-grid (Editable), wherein I can edit the ones that already exist, and/or add new lines and add them to the Invoice_lines table while it maintains a relationship.

Was this reply helpful? Yes No
Suggested answer

stampcoin 5,146 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi @ctrl_kudorje.

I suggest two options:

Import the table via power app make portal -> Table ->Import data (top command area). if you didn't define the tables.
then create the relations between the two tables , Parental relationship behavior.
then build the form and subgrid.

Create the table manually, define the relationship. publish it. Then use data management to import the data.

check the attached image

Was this reply helpful? Yes No
Suggested answer

Fubar 8,487 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
In Dataverse you would avoid linking the way you have. Pretty much everything links via GUIDs.

Your Invoice record in Dataverese will have a unique identifier (a GUID) automatically assigned to it when it is created (in a field with the same logical schema name as the Table but with an "id" suffix. You may consider putting your existing Invoice_id into the Primary Name column (this column is what users see in the Lookup field on child records, but behind the scenes the linkage is actually the parent records GUID), then using an autonumber on the Primary Name column to continue the sequence.

In Dataverse for your line item Table add a Column of Type Lookup (to Invoice) - this will be your replacement one-to-many relationship.

With that structure adding new records into the subgrid etc will automatically be linked via the Lookup column.

Your issue with importing pre-existing data is to get the Lookup field to map to the correct Invoice record. By default the out of the box mapping for the Lookup on the Child record will usually look for the GUID or Primary Name of the parent record, this mapping can be changed during import so the Lookup on the Child record looks for a different field with a unique value.

During Import, set the import so that your Line Item field with the invoice_id is mapped to the Lookup field in Dataverse. (if not using the Primary Name of the Parent record to hold the existing invoice_id, alter the mapping during import to use a different field.

Alternatively, after importing the Invoices, export them (this will include the GUID in a hidden column A) and then populate your Line Items with the GUID, and use the field with the parent GUID map to the Invoice.

Was this reply helpful? Yes No