Anyone else having issues with dropdown options not syncing in the new form builder?
I'm pulling my hair out here. I have a multi-step form with a dropdown field connected to a property. When I add new options to that property, they just don't show up in the form. Not in the editor, not on the live form. Nothing.
The property has the new options, but the form is stuck showing the old ones.
The only "fix" I found is disconnecting and reconnecting the property, but that nukes all your conditional logic. So yeah, not really a solution when you have a form with complex logic built out.
Is this happening to anyone else? Is there a better workaround I'm missing? This is becoming a real pain when clients need dropdown options updated regularly.
The relevant part is cropped in your screenshot, but you should see a suggestion to add unused options / add options. In my example, I added value "d" after the checkboxes had been added previously with values a, b, c.
If you're not seeing that option, I'd recommend reaching out to HubSpot support in-app directly via chat or email.
The subscription doesn't matter here.
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
@PViaene that's been the behavior for the legacy form editor as well, so in that sense it's not new behavior.
Adding an option in a form means that you're selecting from all available options that already exist but are not shown on the form. You're not adding a net new one.
In my case, adding an option meant that the not shown option D was added to the form. I didn't create D from scratch in the form editor.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
The relevant part is cropped in your screenshot, but you should see a suggestion to add unused options / add options. In my example, I added value "d" after the checkboxes had been added previously with values a, b, c.
If you're not seeing that option, I'd recommend reaching out to HubSpot support in-app directly via chat or email.
The subscription doesn't matter here.
Best regards
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer
I see that option as well, but it didn't seem like the most logical way to add options to a property. Properties are typically managed centrally from your settings > properties, and that's how they're centrally controlled.
Now you're adding an option from a specific form.
What if you add an option centrally and the same option from a specific form? Then you need to ensure the CRM Value is identical, because otherwise it can never recognize that it's one and the same option. Correct?
@PViaene that's been the behavior for the legacy form editor as well, so in that sense it's not new behavior.
Adding an option in a form means that you're selecting from all available options that already exist but are not shown on the form. You're not adding a net new one.
In my case, adding an option meant that the not shown option D was added to the form. I didn't create D from scratch in the form editor.
Karsten Köhler HubSpot Freelancer | RevOps & CRM Consultant | Community Hall of Famer