So this issue doesn’t affect existing pages with a Skuid component already embedded using the Lightning Component? Does it just affect building new pages with the builder? Also, does it affect particular versions of Skuid?
A patch released by Salesforce impacted the ability to use the Skuid component on Lightning App Builder pages.
Progress:
Salesforce: We have escalated our case with Salesforce and R&D is investigating.
Skuid: Skuid product engineering published a hotfix (Spark 12.0.11 and Millau 11.2.22) that resolves the issue.
What to do if you are affected?
Skuid recommends testing the hotfix closest to your current version. These patches are 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.
If you are unable to upgrade at this time, please use the workaround offered previously.
I installed the hotfix, but I still don’t see the Skuid Page Component under Custom Components after installing the hotfix. I’ve tried using the Visualforce Component workaround, but it requires that you put in a height (in pixels) of the page which often changes based on the record.
(1) Is there an easy way to make the VF component have a dynamic height based on the page?
(2) Do I need to do something else to use the Skuid Page Component in Lightning Builder?
Hi @“Karen Waldschmitt”,
I am getting this same error this week - perhaps related to SFDC Winter 21 release? Curiously though, System Admin profile is not affected, but all of our other (custom) profiles are getting this error.