Sure. It'll involve some custom fields and WF/PB. The number of those is dependent on how many stages you have.
The general idea is that you have two custom date fields for each stage and workflow rules or a process builder that stamps the date when a stage is entered or left:
Date Entered Stage A
Date Left Stage A
If your stages are linear (one is always ...
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.
Since you have just 20 city names , you can create Entity Code as the formula field to populate it depending on whatever is the value in the Region field.
Alternatively, you can store the mapping of Region and Entity code in the custom setting or custom metadata and access it in apex class/ trigger to populate the entity code , fetching the mapping from the ...
Unfortunately, the only standard way to achieve what you want is the dependent picklist option. You're right to be cautious about changing the Type of your Region field, but this is entirely doable. You can ensure no data issues by either:
Not enabling the 'restrict picklist to only specified values'
Using your existing data to generate a set of ...
Given that Workflow or Process Builder don't trigger on Delete DML (yet) - see Idea and vote it up then ...
Write an AfterDelete Trigger on the object that uses a future or queueable apex class to make the callout
The async class can do the callout synchronously and manage the response directly
Write an AfterDelete Trigger on the Event ...
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 ...
Copying my comment to an answer as it seems it helped.
You are trying to set the result of comparison between your field and number to the result field, the result is Boolean and it does not suit your formula. Just leave it as 1000, that should work.
This is not possible. Formula fields have no stored value - their values are calculated at the time of accessing the data. There is no change event to which you can react for formula fields.
You'd need to build your automation to react to changes to the fields that themselves drive the value of your formula field.
You could potentially implement "ignoring ...
Two main approaches come to mind:
1) Set up conditional visibility
Including two instances of the second input component in the screen
Making one required, and the other optional
Setting up conditional visibility on them so that only one is displayed at a time (based on whether or not it should be required)
You could use decision and assignment elements ...
If there is no relationship between the objects then this is not possible to achieve.
The workflow can only update the same record or the Master record. no other record can be manipulated using just workflow.