APIs & Integrations

Journaway_OK
Participant

Workflow - strings containing a number get parsed to number

Hi,

 

I have a Multiselect-property that has numbers as internal values:

Public ValueInternal Value
Prop A

1

Prop B2
Prop C

3

 

Now when I have multiple Values selected, then it is not a problem at all, but if there is only a single value selected, then using Workflows calling a webhook with POST and selecting specific properties instead of sending a complete Deal causes the property to be sent as a number although I expected the value to be a string containing the number.

 

 

//With multiple values
{
  "propertyName" : "1; 2"
}

//With single value
//Expected
{
  "propertyName" : "1"
}

//Got
{
  "propertyName" : 1
}

//Also happens when strings contain spaces after a number
//Expected
{
  "propertyName" : "1 Hello HubSpot"
}

//Got
{
  "propertyName" : 1
}

 

 

This also happens if a textfield which has a space after a number.

0 Upvotes
2 Replies 2
Jaycee_Lewis
Community Manager
Community Manager

Workflow - strings containing a number get parsed to number

Hi, @Journaway_OK 👋 Thanks for reaching out! One question before I go all the way down the rabbit hole  — have you already contacted support about this issue? I would rather not put you in a frustration-loop if at all possible.

 

If not, this one is a good candidate. I can assist in this case if needed. Just send me a DM. Otherwise, we can work on it here.

 

I am curious, @Teun @LMeert @miljkovicmisa, do you have any thoughts or initial troubleshooting steps @Journaway_OK can try?

 

Thank you for taking a look!  — Jaycee

linkedin

Jaycee Lewis

Developer Community Manager

Community | HubSpot

0 Upvotes
Journaway_OK
Participant

Workflow - strings containing a number get parsed to number

Hello @Jaycee_Lewis ,
Thanks for the hint!

For some reason, I completely forgot about that. I just contacted them.

0 Upvotes