Skip to main content

After upgrading our production org to 11.1.8, we are seeing a user side error on inaccessible fields. I understand there was a recent change to Skuid to show page builders inaccessible fields on the design side, but now we are seeing different behavior on the user side.


We have a case with a condition on a model, and the condition uses a field that the user may not have read access to. Pre Skuid 11.1.8, the condition would just be ignored. Now on 11.1.8, the user sees red bars saying a model condition is using a field that they don’t have access to.


Is this to be expected?


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.

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings