Pipedrive - different behavior for same fields in different actions

[Finspro]

Hi there,
i realized that for the same application, when working with different actions, the fields are handled differently.
My example Workflow is this one: workflow/mapping/IjU3NjYwNTZlMDYzMjA0MzY1MjY4NTUzZDUxMzUi_pc

For example:
Field: Label (Standard field)
Action: Pipedrive : Find or Create a Person
Here it shows the values behind the Picklist-field available for selection.
Also, it shows the field 2x in the same action step in the list of fields, both with picklist selection, leaves me not sure which to use.

Action: Pipedrive : Update Person
Here it shows as empty field and let me just map from previous steps or manually enter data.
Also, it shows the field 2x in the same action step in the list of fields, both for entering manually data, its wrong and leaves me confused as well.

Field "Besitzer" (Owner) is also not shown as picklist field.
Also for custom field like "Immobilienbesitz" (just as example). In the middle step for Update Person, it will show as Textfield with mapping of the steps, but not as the Dropdown selection, like in Find or Create a Person or the next Step Update Person with Custom Fields (where i have the dropdown select field values).

These are examples, but as i currently evaluate to migrate from zapier to pabbly and quite often i have the feeling it is a bit of gambling which Action does or contains what exactly, i want to ask you, is there any kind of logic behind these differences?
Or that i have multiple instances of the same field in one Step?

This approach makes it hard to get fully convinced.

Thank you very much in advance for your hints

Best regards
Christian

 

[ArshilAhmad]

Hi @Finspro,

Please allow me some time to discuss this with my technical team. We will get back to you with an update soon.

 

[Finspro]

Good morning @ArshilAhmad ,

thank you, of course, i will be happy to hear from you and provide more information if needed.

Regards
Christian

 

[Preeti Paryani]

Hello @Finspro,

Our team has made a few updates, and here’s how the actions will now function:

• Label Field (Standard Field): You will see two label fields in the action step:
  • One allows you to select a single label.
  • The other, labeled as "Labels", allows you to select multiple labels.
  • We understand this may be a bit confusing, but this structure cannot be changed as it might impact existing workflows.
• Owner Field ("Besitzer"): Instead of a picklist, you will need to map the User ID. You can retrieve this ID using the "Get All Users" action. This issue has now been corrected in both actions.

Let us know if you need further clarification!

 

[Finspro]

Hi @Preeti Paryani ,

thank you for your feedback - although i would have expected the picklist-values out of the triggered system whereever possible, at least as long as it is consistent, it is ok.

Regarding the Labels, it is REALLY confusing ... not sure why this is setup this way when you work with same Application field.
But ok, thank you for setting the values in Owner field at least.

Regards
Christian