That error message is part of a "gack". Gacks are salesforce internal errors that you can't usually fix on your own. Think of them as an unhandled salesforce error.
Theres a lot of resources out there about gacks but at the end of the day they all say the same thing - only salesforce knows what this error means and only salesforce can fix it.
What is a ...
I think you are trying to do a histogram for picklist values.
I have done something similar with Status field on the Case Object. We use the case history object and we have history tracking enabled on the status field.
We query the case history object for the record to create the status change by time. We are use the same dataset to create multiple ...
The error message
Error Occurred: Probably Limit Exceeded or 0 recipients
is explained in this help document
I'm assuming you have some sort of email alert going out as an action on your process builder. This email alert is trying to send an email, but there's no recipients or the recipient is a user who is inactive.
If you want to execute action only when the Due Date is edited, select "Formula evaluates to true" for Criteria for Executing Actions* and the formula should be something like-
(ISCHANGED([Loan_stock__c].Due_date__c) && !ISNEW() //if its not a new record
Include other criteria's as well(which you have mentioned above in question) in ...
That's right Ayush, in the criteria within the Action itself, you cannot select fields on related objects.
Either put the Account owner email criterion in the diamond criteria node, or add a custom field to your object which gets the Account owner email.
There are lots of cases where a user shouldn't be allowed to update a field value, but that value may still be legal. For example, perhaps a Status field allows me to set the value to Pending or Canceled, but not Approved. In order to Approve a record, an Approval Process must be followed. In that manner, the manager can approve the record, but the user can'...
In answer to your direct question: why would you set up a field update to put in bad data on the object? Ideally, a field update that's automated would be using "correct" data
Otherwise, I think the general question (using which automation tool) is a complicated one that has a degree of opinion and differences on a case-by-case basis.
However, in ...
Depends - if it's a process builder operating on the update/creation of an object then the objects already exist and filtering is similar to how you'd do it in an apex trigger context. If you're doing a Get Record component in flow then it'd be a query.
I believe yes although I can't find any documentation that outright says it. Note that workflow field ...
Platform event was triggering. It was not present in logs as I thought it would be.
Narender Singh on https://success.salesforce.com/answers?id=9063A000000eWWGQA2
Suggested I create a process for the event to confirm it fired on the PE event.
Following this - I confirmed the event fired.
If Process Builder has Invocable class and that class is not covered when PB is deployed via change-set then we have to select this option in Org "Process automation setting" : Deploy processes and flows as active SF link.
After this try to re-validate change-set, test coverage of class will be covered as per written test class.
The only main problem you should be aware of is that your process builder must not call the future method recursively. This would happen because the future method performs some sort of DML operation (usually an update) that causes the process builder to fire again, and calling the future method while already in a future context. As long as you remember to ...
You should be able to do this through a metadata deployment. If you have a test environment, you can try this out to see if it works. In API version 44.0 and later, you can do this all through the Flow metadata type (no need for FlowDefinition).
You'll want to ...
There's no way to do this synchronously (within the same transaction), so there's always going to be the possibility that partner users could see the original Last Modified By information. You can't ever change the running user within a non-test transaction.
To change the Last Modified By user, you'd need to fire a Platform Event from a trigger, which will ...
Thanks for your thoughts and inputs guys. It is a Date field but on other the other object. The object on which I'm building the PB have a Lookup relation with that object and I though PB can read those related fields too. No I have to build a new PB on that object as I cannot use formula field.