New answers tagged

0

Yes, Everything is perfect. Here what's happening is I have two workflow 1. time-based workflow(to make case status as "CLOSED" and 2. normal workflow (to send email alert). our functionality work as whenever the case resolved it will enter into time-based workflow and it will wait for 24Hours then change the status to "closed" after that ...


0

Did you check the email logs? Order the email logs and check if the email is fired from Salesforce. If it is fired from Salesforce then the issue is with the server of the email domain.


3

Salesforce was founded in 1999, and by 2000 was branded as the "No Software" CRM solution. For the first eight years or so, there was no code-based alternatives, and it worked well enough for many small-to-medium-sized orgs. Apex was largely made as a stopgap for those large orgs with highly specialized processes, which took many years and ...


3

Updating an OrderItem automatically causes the implicit Rollup Summary on Order.TotalAmount (i.e. the Sum of OrderItem.TotalPrice) If you have any other RSF on Order that reference OrderItem children, they will be recalculated in Step 16 of the Triggers and Order of Execution If the record contains a roll-up summary field or is part of a cross-object ...


1

You'd want to use Process Builder to have multiple conditions like that, or even better, a Before Save Flow or Before Insert/Update Apex Trigger to avoid triggering DML triggers twice. Workflow Rules don't allow setting the value dynamically for picklist values.


0

Your workflow seems to be correct just wanted to let you know that "id fields return 15 digit ids in workflow" so if you are using 18 digit created by id, your workflow will not work


1

If you have the flexibility to mark the records that require processing in some way you can then indirectly use a scheduled batch to deal with the end results of the over-all transaction/session. We do this by having two Datetime "timestamp" fields, LastProcessed__c and LastUpdated__c and a Checkbox formula field NeedsProcessing__c set as NOT(...


1

What I sometimes do is use a platform event to get out of the context and then I can avoid a queueable altogether. I define the platform event (normally just with a payload var that is a serialized map with all the params. Then, fire the event and in the event handler, unpack the event which has these params: className callableMethodName callableParams Here ...


Top 50 recent answers are included