Thank you very much @Designer-Kyle , makes much more sense now!
Regarding the "Conditional property options", you mentioned it is currently in private beta and thus the feature will work only when creating records. Do we know when we can expect to be able to have this feature apply also when editing records?
Thanks again!
Would be amazing to have the same functionality on forms too
@Designer-Kyle Do you know if you will roll out conditional properties for Products since that is considered an object as well?
@Designer-Kyle
@rwebb1
Hey! How can we know some info about Conditional Property Options via API?
There is no info in the response:
https://api.hubapi.com/crm/v3/schemas/companies
Hi - Is there any reason Pipeline is unsupported as a controlling property?
Super cool update - I’d love to see this applicable on lead capture forms! Will this be in the roadmap?
@Designer-Kyle Thanks a lot for detailing the different betas - it’s great that both these amazing must-have features are in the works. But I think either I’m misunderstanding this or you got the betas mixed up. The public beta that I’m able to find in the ‘Product Updates’ section allows me to control which options appear in a property based on a choice in a controlling property.
I’m looking to require additional properties based on a selection in a controlling property. Example: When the property “Lead Status” is updated with the value “Unqualified”, I want the drop-down property “Unqualified Reason” to show up and be required. For all other values in “Lead Status”, “Unqualified Reason” need not be filled (so I don’t want it to show up even). Is this in private beta and I can request for it via my Customer Success Manager? Thanks!
Is there a plan for Conditional Property Options to be available in Forms? For example if someone has selected Industry X then they can only select from Sectors XYZ. It’s working when manually creating a Contact but not in Forms.
Also, would an import error if the Sectors weren’t XYZ?
Hey @rwebb1 ,
Long awaited function!! I’ve setup the logic on ticket records it works pretty well.
Will the conditional property options be available on Forms as well? We have a support form where it would be a huge help! I’ve tried applying it however it did not work.
Thanks,
Janka
Hi all! Rachel from the HubSpot Product team here. Both Conditional Property Logic (surface/require properties depending on the value of another property) and Conditional Property Options (specify which options are shown for a property depending on the value of another property) are out to all Hubs, Professional+ subscription.
This functionality does not currently apply to the Forms tool - our teams are taking this feedback into account for future planning. Thank you for your input!
Much needed feature. With the mandate to drive more personalisation without creating a complex web of similar properties, we need this functionality urgently !
This week I had this stopper: I’m preparing a form for an offline event that takes place in different cities.Depending on the city the contact chooses, some events or others should appear. There are some events that are the same for all cities and others that are not.
So that the form would be more usable and attractive to fill out, I’ve been trying to leverage a single property with all events and use an “event city” property to filter the conditional fields.
After several attempts, the only solution is to create a property for each city…
I hope this can be improved.
Same, I’m bumping this. This should be added to the form as well; we have clients with more than 50 restaurants. If they could filter by restaurant type, that would be really helpful.
This would drastically improve the forms experience and make sure we only surface relevant property values!
@rwebb1 Do you know if this will be considered for forms in the future now that we have multi-step forms? A customer called support requesting the ability to have a dependent field but control the dropdown values that show on the dependent property. +1 on her behalf.
Updating here that I checked with product and this still isn’t a functionality with the tools for forms, just dependent form fields. It’s been discussed but it isn’t planned at this time.
Our team wants to build conditional logic where if a property is marked as “yes” then have the option to have an open text field populate underneath as required. Why is there a limit on only allowing conditional login with dropdown/multi-select fields? Open text would be very helpful to include as well. Thank you for considering.
It’s insane that 4 years later this still isn’t delivered. It already sucks that we have to use the properties on one of the objects in a form, but it’s made even worse because we can’t hide some of the dropdown options for a given property on some forms that we don’t want to show all of them.
