I checked my affected user and she has ONLY read access to pages.
Hi Mark,
Limiting access to just “Read” seems to have fixed the issue. Is there a reason to give them access to Read?
Chandra, as Mark mentioned above perhaps your affecting user is being granted permission somewhere else.
Andrew - read to the bad field? Or to Pages. I don’t see any place where my user has edit access to the Pages object. I have checked her profile and all 5 perm sets.
Andrew, to clarify: the deciding factor on whether these errors are visible on the page is whether or not user has read access to the Pages object. If they do, it means they have Skuid Page Builder and/or Skuid Page Admin permission sets, and should see field accessibility errors.
On Friday, we discovered that these field accessibility errors are being shown on the page for Skuid Page Viewers, but only if the following is true:
1) the model has a condition using an inaccessible field
2) the model is being queried by the Action Framework (i.e. not the model’s initial query on page load).
We will keep you up to date on this Community thread as we have further information.
Wondering if a status could be provided on this investigation.
Hi David,
The issue is known to our development team. The fix doesn’t have a release date yet, but it should be in an upcoming maintenance release. My response above, from April 30th, explains the product issue that can cause these errors to show on the page. Just to clarify though, the first thing you would want to do is rule out any legitimate reasons for these errors to show on the page. For that, please ensure that all field accessibility settings are accurate, and that the affected user does not have the Skuid Admin or Skuid Page Builder permission set, and doesn’t have edit access to Skuid’s Pages object.
Thank you for your patience! Skuid has fixed the issue in which Skuid Page Viewers would “inaccessible field” Skuid error, but shouldn’t (issue CORE-1789) in the new 11.2.2 release which is now available on the Skuid Releases page.
As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes when you upgrade. Please let us know if you continue to encounter any problems with this issue after upgrading.
Thanks again for alerting us of these issues!
Users were seeing this on their end (not in the builder) when we used a page include
Updating to Spark (12.0.4.0) fixed the issue.
