In a flow, it’s usually a good idea to keep the labels of elements short and sweet. For example, you don’t need to specify which field(s) you’re actually updating in an update element.
I’ve seen consultants use “Update Billing Address on Account” for such an element. This may be OK if and only if Type is the only field being updated. But a better label would be “Update Account”. This way you don’t need to change the label when additional fields are updated.
But if your flow has multiple “Update Account” elements, what then?
Well, only the element’s API Name needs to be unique, not the label. So you could have
- Label 1: “Update Account”
- API Name 1: “Update_Account_Type_Does_Not_Exist”
and
- Label 2: “Update Account”
- API Name 2: “Update_Account_Type_Exists”
The takeaway
In flows, keep labels concise, and don’t be afraid to use the same label multiple times.
Category:
Salesforce