When designing a PowerApps App, I encounter this run time error 'The requested operation is invalid. Server Response: Number of link entities in query exceeded maximum limit'.
I trace the error and it is related to an entity called 'Projects' I used in my app. I have a gallery with data source as 'Projects'. I have another form to edit the project. When I set the form item to GalleryProject.Selected, the run time error appears.
But if I save the app, quit the design mode and just run the app, the form seems working. The form doesn't work only in design mode because of the run time error above.
What is the cause of error and how to work around it? Thanks much!
Hi @LiZhixian ,
Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned.
Please consider take a try to set the Item property of the Edit form to following:
LookUp('Projects Entity', 'Unique Identifier Column' = GalleryProject.Selected.'Unique Identifier Column')
then check if the issue is solved.
In addition, you could also consider save the selected Gallery Item into a variable, then use the variable within the Item property of the Edit form. Set the OnSelect property of the Gallery to following:
Set the Item property of the Edit form to following:
Note: Please make sure the Edit form has been connected to the Projects Entity already
Also please make sure you have turned on the "Formula-level error management" option within Advanced settings of App settings of your app, then re-load your app, check if the issue is fixed.
Thanks for the reply. I did try using variable for form item, but the error is still there.
After many tests, there is one more observation that the error is linked to 'look up' field. My entity 'Project' has many look up fields. After adding certain number of look up fields to the form (may be 10), the error appears if I add one more look up field to the form. But there is no error if I add few more text fields to the form.
I think for look up field, it requires 'join' to other table when query in DB. And there is a constraint in number of 'joins' checked by system (not likely the DB, but maybe some middleware) due to performance consideration. Could this be a possible reason? If yes, how to overcome this? 10 lookup field in a form is too few.
Hi @LiZhixian ,
Yeah, based on the issue that you mentioned above, I think this issue may be related to the amount of LookUp fields in your Entity.
Actually, it is an known issue with LookUp fields in CRM Entity, please check the following article for more details:
Currently, there is a limit on the amount of the LookUp type fields in CRM Entity/CDS Entity -- we could only add 10 LookUp fields within a CRM/CDS Entity.
As an alternative solution, please decrease the amount of LookUp fields in your CRM Entity, instead, add Text type columns to store the value (e.g. store the 'Unique Identifer' column value from your Referenced Entity). Then within your canvas app, you could find the corresponding record in referenced Entity using LookUp function based on the Text column value.
Note: I think this issue may be related to data source itself rather than PowerApps.
Check it out!
Check it out!
Fill out a quick form to claim your user group badge now!
Find out where you can attend!
Features releasing from October 2019 through March 2020
The largest Power BI, Power Platform, and Data conference in New Zealand