Recently working on a more complex table permissions scenario on Power Pages, where we required a N:N relationship relationships with more levels of child permissions, we had nice results when using out-of-the-box lists and also with Liquid custom Web Templates.
However, I noted a few errors with basic GET queries in the WebAPI such as:
{"error":{"code":"9004010D","message":"Common Data Service error occurred.","cdscode":"0x0","innererror":{"code":"0x0","message":"Could not find a property named 'mypref_mypref_item_contact' on type 'Microsoft.Dynamics.CRM.mypref_item'."}}}It turns out this is a known issue when Parental, Contact or Account scopes add additional conditions to the query, as reported here.
To overcome this issue, whenever using such type of relationship and calling the Web API, the recommended approach is to use a FetchXML filter in the querystring, so the issue will not happen.
Note that the FetchXML filter in the querystring needs to be encoded…
Source link
More About This Author
-
SharePoint and Office 365 Consultant/Developer always trying to get the best from Microsoft stack (Microsoft 365/Azure/Power Platform and related stuff).
Living in Ireland since 2018, I had previously worked in Brazil as a consultant/developer for Office 365, SharePoint and related technologies for almost 10 years.
Array
Modern Workplace19 November 2023Ignite 2023: Curated blog posts with Microsoft 365 & Power Platform Updates
Modern Workplace4 November 2023Getting the proper SharePoint list columns internal names to use in List Formatting JSON
Modern Workplace25 October 2023Create parent and child records with a single WebAPI call in Power Pages
Modern Workplace21 October 2023How to allow users to only Add and View SharePoint list items (block editing/deleting)
