New answers tagged

1

There's a note at the bottom of this help document that clarifies there was a recent change (Summer '19) that is causing your issue Please note as of Summer Release 19', Users must have a verified email address and .invalid removed from the email address in order to send email alerts via Workflow, Process, Flows or Triggers. I didn't find any note about it ...


1

You need to convert the criteria into formula where you can easily access the ISNEW function which evaluates to true if record is created. You can access ISCHANGED(field) function as well.


2

Right-click on the validation rules folder for the object, and click SFDX: Retrieve Source from Org.


1

It turned out to be that the page depended on some HTML files in Prod which were saved in Salesforce Classic under Documents. Documents don't get copied over, and so those dependencies were broken. Those HTML files were loading jQuery as well as some other things needed. I went into Prod, downloaded them, and had to go into Salesforce Classic to upload them. ...


0

It's possible that you need to set up permissions for your component to load the external jQuery library. Try going to Setup > CSP Trusted Sites and make sure you have an entry for https://code.jquery.com/. If there is no entry, click on New Trusted Site and add https://code.jquery.com/. Make sure you check the checkbox for Allow site for connect-src. If ...


0

You can use $Api.Enterprise_Server_URL_500 to get the url and then see if it contains your production or sandbox name. if( CONTAINS($Api.Enterprise_Server_URL_500, 'fullsand'),'sandbox','production') or just leave it as binary. You can also do this to have dynamic urls when using sandbox links. Just make sure that the url has the contains clause. it get a ...


Top 50 recent answers are included