I have 3 entities in CDS to store the many-to-many relationship between students and test campaign.
I import the data source into PowerApps as 'GMT Students', 'GMT Campaigns' and 'GMT Tests'
'GMT Tests' is the intersection table to record this many-to-many relationship, data structure as below
And I use below script to load the student, test campaign and the registration data into variables.
Set(CurrentStudent,LookUp('GMT Students',Email=Trim(txtEmail.Text))); Set(CurrentTest,LookUp('GMT Tests','GMT Student'.'GMT Students' = CurrentStudent.'GMT Students')); Set(CurrentCampaign,LookUp('GMT Campaigns','GMT Campaign'=CurrentTest.'GMT Campaign'.'GMT Campaign'));
The CurrentStudent was loaded as expect, but CurrentTest has some strange result which has no GMT Student and GMT Campaign included.
But it does exist when I look into the entity data
Actually it does work days before and I really don't know where is wrong.
Thanks for any help.
Have you tried to restore your app to a previous version to have a test? https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/restore-an-app
Hi there, I had the same issue, I was told it is by design, but by all accounts they are looking to resolve the display issue.
I could not get it to work but I was told that you can still use the data in the field to do relational lookups but I could not get it to work.
I think it can't be simply closed by "by design"
At least, there should be a "best practice" suggested from product team on how to get data from join table.
Now I'm stucked here...anyone from support/PG team can help?
As mentioned in the following thread, seems like it's a bug (or by
stupid design) and there is a workaround solution for that.
You need to add a column from the data source that is referencing in the lookup.
ClearCollect(ContactCollection, DropColumns( AddColumns( ShowColumns(Contacts, "fullname", "createdby"), "tempUserColumn", First(Users).User ), "tempUserColumn" ) )
This needs to be fixed urgently. It has broken previously functioning apps in production which is unacceptable.
The behavior change is not consistent with "Lookup to second level tables" specified in this post back in August: https://powerapps.microsoft.com/en-us/blog/preview-for-improve-data-source-experience-and-common-dat...
Check out the on demand sessions that are available now!
See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.
ISV Studio is designed to become the go-to Power Platform destination for ISV’s to monitor & manage published applications.
Features releasing from October 2020 through March 2021