Bug when using option fields for automations
Some of our protégés use automations to standardize deal names. They do this by using single (or multiple) option custom fields. In my demo case: "Dealquelle" = source of the deal.
So in this example the workflow changes the deal title like
[Dealquelle] - [organisation name] - [contact name]
Works quite well.
If you are adding a single option it doesn't work anymore with the text. Instead, Pipedrive uses the value of the option (I added Pipedrive Webform):
It works when I go back to the automation, open it and resave it. By doing this, everything is fine:
If you know this, you can handle it. But there are situation when not the creator of the workflow ads a new single option. And it is just the creator of the workflow who can access it and re-save it. This can cause serious troubles.
Do you see the urgence of fixing this? I know somebody who needs a project ID for each deal. So there are tons of new values all the time. I have already informed the support about this at least one year ago. Would be great if this works properly soon!