Closed aKasperavicius closed 4 years ago
Starting in Winter '21, all users accessing @AuraEnabled Apex methods must have specific authorization to access the class in their profile or a permission set. In this case, you must assign access for SObjectController2.
Using the Deploy to Salesforce button does not update any listings in "Installed Packages" because the components are installed individually rather than as a package.
Wow, thanks much for the link and shame on me for not cluing in on this from the update release notes. That makes sense. Thanks for a great tool and greetings from Berlin!
Glad that this is working again for you and greetings back to you from Maine.
On Sat, Oct 17, 2020 at 11:52 AM Alexis Kasperavicius < notifications@github.com> wrote:
Wow, thanks much for the link and shame on me for not cluing in on this from the update release notes. That makes sense. Thanks for a great tool and greetings from Berlin!
— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/ericrsmith35/DatatableV2/issues/47#issuecomment-711033717, or unsubscribe https://github.com/notifications/unsubscribe-auth/AF4UHX4LGNSBJ3JK4PP2723SLG4T7ANCNFSM4SUG4GQQ .
Flows using this component in my (just updated) Winter '21 sandbox or production orgs cannot be opened, deployed or even downloaded using workbench. It's as if the flow XML files no longer exist.
Further, the DatatableV2 package no longer shows as installed. Attempting to re-install seems to be successful, however the package is still not listed in the org and when making a new flow, DatatableV2 is not available as a component to use.
It was working perfectly last night and this morning, after the Winter '21 upgrade, all flows using it display the following error:
Something went wrong Hmm, that didn't work. Reload the flow list page and open the flow from there. For help, contact Salesforce Customer Support. Error ID: 1685530200