Can't See related records in Powerapps or dataverse

(0) Share

Report

Posted on by YoavOrion

Hi,

I have a table of records which is related in a one-to-many relationships to another table of records.

'table 1' has many records related to it in 'table 2'. I also see table 1 record's GUID in the related records in table 2 when i edit the data in excel.

The problem is that when i try to view the related records in powerapps gallery or in datavers record editor via subgrid, they do not show. in powerapps i use in items property: table1record.table2 but is has no records in it.

all the records are in Active status.

what can be the issue?

Thank you

Yoav

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (4)

Answers (1)

YoavOrion 27 on at

Like (0)

Report

Ok I found the problem but don't know how to fix it.
The tables are records I am importing from SharePoint and I am using the SP ID columns as a unique ID and an alternate key. the tables are getting associated correctly meaning I can see the correct lookup from table 1 at table 2 lookup column BUT the GUID of the "ONE" table doesn't match the GUID on the lookup at the "MANY" table.

something get terribly wrong when importing using alternate key... HELP!

Was this reply helpful? Yes No
Ram Prakash Duraisamy 5,593 Super User 2025 Season 2 on at

Like (0)

Report

Hello @YoavOrion,

As per your scenario TABLE 1 Value will be lookup to TABLE 2, correct me if am wrong

Please mark as Answer if it is helpful and provide Kudos

Subscribe : https://www.youtube.com/channel/UCnGNN3hdlKBOr6PXotskNLA
Blog : https://microsoftcrmtechie.blogspot.com

Was this reply helpful? Yes No
Drew Poggemann 9,287 Most Valuable Professional on at

Like (0)

Report

Hi @YoavOrion ,

In the Dataverse you create a 1:N relationship through a Lookup field and the Lookup field is based on the "Primary Name" column of the table with the 1 side of the relationship. Example in your situation here you would need to populate the name field on table A with the SPID value and then in table B you would import the records setting the Lookup column for table A to the SPID from the 1 side of the relationship.

Thanks,

Drew

Was this reply helpful? Yes No
Verified answer

YoavOrion 27 on at

Like (0)

Report

Thanks @dpoggemann. the problem was solved. apparently i had duplicates in my alternate key which i guess created the problem.

Was this reply helpful? Yes No