Hi Karen! I hope you’re well.
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?
Cheers! Louis
Hi Louis!
Good, thanks for asking. Hope you are doing well also!
Customers are reporting problems with existing pages that were being used in production orgs up until they started seeing the errors …
We have heard reports of clients on multiple versions of 11.2.X and 12.0.X and also a variety of Salesforce NA, EU, and AP Salesforce instances
Thanks!
Karen
Hello,
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 Sam,
It sounds like you may not have My Domain set up in your org. You can read about this here: https://docs.skuid.com/latest/en/skuid/deploy/salesforce/lightning/#salesforce-lightning
Let us know if this is set up, and you’re still not able to see the Skuid Page Lightning component.
smh, I had it activated, but forgot to roll it out to users. Now it’s working. Thank you!
Is there a difference in performance (query/load times) with the Visualforce method vs. the Skuid lightning component?
Update:
Salesforce released a patch that resolves the issue. If you upgraded your Skuid versions, you are now doubly set
If you are still affected, please let us know by sending an email to support@skuid.com.
Thanks!
Karen
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.