Creating Deal - With Select Field - Options - With characters Å Ä Ö in options
SOLVE
Hi
I am trying to create a deal to my account 2787302 with several dropdown properties (select / options in html).
Problem is that both label and value contains the letters Å Ä Ö in hubspot and when posting a new deal I get this response with a lot of \\\ XXX numbers.
How can I convert my options so that it gets understood at hubspots end? I cant change the property values and labels since it is being used in general - so I need to find a way around it. I am working in PHP if that helps in your answer.
My guess is that I need to convert å to \\\\303\\\205 and so on for all the letters before posting it - but there should be a smother way. Also I dont know all the \\\\CODES for all the letters not being supported.
{"status":"error","message":"Property values were not valid: [{\"isValid\":false,\"message\":\"årsomsättning was not one of the allowed options: [label: \\\"\\\\303\\\\205rsoms\\\\303\\\\244ttning\\\"\\nvalue: \\\"\\\\303\\\\205rsoms\\\\303\\\\244ttning\\\"\\ndisplay_order: 0\\ndouble_data: 0.0\\nhidden: false\\ndescription: \\\"\\\"\\nread_only: false\\n, label: \\\"Antal verifikat per \\\\303\\\\245r\\\"\\nvalue: \\\"Antal verifikat per \\\\303\\\\245r\\\"\\ndisplay_order: 1\\ndouble_data: 0.0
Creating Deal - With Select Field - Options - With characters Å Ä Ö in options
SOLVE
Solved:
After a few hours of searching the the problem seemed to be completly unrelated. There was two similar properties with the words in different order. So using special characters simply does work as it was suppose to (tested and confirmed) - the issue in this case was my blindness.
Sorry if any time was spend on it. Leaving my answer for future use by others.
Creating Deal - With Select Field - Options - With characters Å Ä Ö in options
SOLVE
Solved:
After a few hours of searching the the problem seemed to be completly unrelated. There was two similar properties with the words in different order. So using special characters simply does work as it was suppose to (tested and confirmed) - the issue in this case was my blindness.
Sorry if any time was spend on it. Leaving my answer for future use by others.