Power Pages: a known table permissions issue which I did not know were known
If you've been experiencing issues with Power Pages Web API calls, specifically receiving an error message about a property that doesn't exist but might have existed, there is a known issue with a workaround. You can disable the OData filter for the problematic table by adding a site setting, which should solve the problem. Make sure to sync your changes. This workaround has been successful for others. Additionally, you can explore alternative solutions like FetchXML.
Article 4m
Login now to access my digest by 365.Training
Learn how my digest works
Features
- Articles, blogs, podcasts, training, and videos
- Quick read TL;DRs for each item
- Advanced filtering to prioritize what you care about
- Quick views to isolate what you are looking for right now
- Save your favorite items
- Share your favorites
- Snooze items you want to revisit when you have more time