Indeed this should be reaching also Deals, Contacts and Companies creation, so whenever you create a contact with linked properties the logic behind should define relationship, so Level 1 combo options should relate to Level 2 combos related options.
We are in dire need of this for our users. Being able to surface the properties that really matter based on certain conditions would help our data quality and overall adoption greatly. As it stands, we either have to make every property visible at record creation (but not required, therefore users can and will bypass input), or, we have to create a conditional view which would require a page refresh every time, even if you built out different views for every possible if/then combination. Really surprised this hasn’t been put into development yet as it is available on every major competitor platform. The basic logic already exists on forms, why not record screens?
Rooting for this feature. Sorely needed by Support team for ticket properties!
YES! We have sooooooo many properties but many of them are only necessary based on another property. We could drastically reduce the amount of clutter in the About sections if only the necessary properties were shown.
Gosh I can’t believe this has been around as a request for 4 years with no movement on the HubSpot side. This is such a basic and essential quality of life feature, especially for medium and above sized companies where a single object might contain very different deal/contact/company types that require different properties based on the type.
Problem Solved: You can now create the pipeline for forms where the new properties are shown in the Contact, Company or Ticket form according to the conditions given. Go to edit forms and you will find a new feature ‘Add Pipeline logic’. Thank you @hubspot for adding this feature. It really makes our properties clutterless.
Does this only apply in ServiceHub? Is there a way to do this for Contact Properties? We’d like to be able to set Lead Status with sub-reasons that only become available once “recycle” or similar is chosen.
What about deals? My use case is that when a lost deal reason is selected, such as “missing feature,” we want a submenu to appear with a set of drop-down options.
I have the exact same need. Deal properties to only show or be required to be entered based on the value of another property. Example being if Closed/Lost Reason = X, then require Property Y to be filled out too. @hubspot is there support for this?
Did this got implemented in the meantime or is there any known workarounds?
We just started with HubSpot a week ago and this is a feature I am missing
Yes that’s vert cool but it would be better if the pipeline logic include the properties conditional display : when a pipline is selctionned, i can see only the propreties i want !
This is not what is actually needed. It is needed on an object field level. This may be nice for a pipeline level but not at the object level.
+100000
I have been asking for this same item for a couple of years now. We are to the point where we may need to switch to a different platform that offers such logic. I don’t know if Hubspot cannot figure out how to do this or not. Seems like it should be fairly simple.
Piling on here, but need to add my own disbelief that conditional logic is so absent from different areas of Hubspot
I want this too…this would keep me from moving to SalesForce!!!
Oh man…me too! And coming from a former HubSpotter that used to SELL HubSpot (and had to battle Salesforce in pretty much every deal). This functionality is so mission-critical for us that we’re going to have to swap to SFDC if we can’t get this functionality
Come on @hubspot get this done.
Hi @msjain and everybody,
Thank you for reaching out to the Community and for your valuable Product feedback!
I’d like to share these resources which might be of interest to you:
- The solution from @Mike_Eastwood on this similar post “Conditional properties”
- Add conditional logic to the create record form (Professional and Enterprise only)
- Use dependent form fields
I have found this similar idea already submitted: “Conditional Properties”.
I’d recommend supporting the Idea with an upvote and explaining your use case in the comments.
Our product team uses that forum to collect ideas on how we can improve the product for our customers.
Product pays particular attention to the top voted ideas & takes them into consideration along with other feedback channels as well as their own vision to understand what features will be most valuable.
Thank you and have a lovely day!
Best,
Bérangère
Unfortunately, I can’t see how the suggested resources help our various use cases. Especially for deals - ex: we have a matrix for pipelines and deal types. For the expansion pipelines, we only want to see deal types upgrade, up-sell, plan change, and cross-sell…and not have those deal types available for choice on any other pipeline.