3

This is not yet on Trust it seems. But there is a Communities outage and is affecting a wider audience and is mentioned on the Help Site [I should mention that I got this information internally within my team]


2

This appears to be global. This error message is hidden in the dom with just a white page appearing. "This page has an error. You might just need to refresh it. Assertion Failed!: Failed to find definition for dependency: force/customPerms : undefined Failing descriptor: {markup://force:salesforceScopedModuleResolver}" here's a google search that appears ...


2

Another approach with using URL.searchParams: The searchParams readonly property of the URL interface returns a URLSearchParams object allowing access to the GET decoded query arguments contained in the URL. connectedCallback() { const param = 'test'; const paramValue = this.getUrlParamValue(window.location.href, param); } getUrlParamValue(url, ...


1

As the documentation says, you can't use lightning:overlayLibrary in Lightning Out. You'd need to use your own. You might look at strike_modal instead. You'll need to create a component that will dynamically create the other components, and your dependency app must list all components that will be used dynamically.


1

Your types simply don't match up, as the error is indicating. You declare: public List<Messaging.SingleEmailMessage> createEmailMessage( Id templateName, Id orgEmailAddress, Id targetObjectId, Id whatId, Id accountManagerEmail, boolean accountManagerStatus, Id accountOwnerEmail, boolean accountOwnerStatus, String ...


Only top voted, non community-wiki answers of a minimum length are eligible