HubSpot Ideas


Field Dependencies for Contact Properties

I would like to set up field dependencies for Contact Properties, to ensure that my Sales/Marketing team are updating contact details correctly.


For example, I would only want certain fields to be editable against a contact record if another field against the contact had a certain value.




HubSpot Updates
Being Reviewed
December 14, 2021 09:45 AM

Hi folks,

I’m Shay Jones, the Product Manager on the CRM product team.


Thank you all for taking the time to submit, upvote, and comment on this Idea. We hear you loud and clear, and we agree that this functionality is important. We are currently evaluating if this Idea is feasible and, if so, how our team will implement it. 


Any news about this feature request will be relayed on this thread, so stay tuned!


Not Currently Planned
May 13, 2021 09:01 AM

Hi all, Jeff from the CRM product team. This is a great idea. We will consider it for the future, but we're not working on it actively today.

Please keep the use cases input coming, we're reading every comment on this thread.


April 28, 2021 03:39 PM

Hey HubSpot community, I'm Jeff from the CRM product team.


I realize implementing this wish has taken much longer than anticipated - much longer than we expected as well. We believe what we're focused on right now is higher priority. Rest assured this has not left our list, and Dylan and I continue to read every comment left on here. No timeline update on this functionality at this time, hope to be back someday soon with more details.



Being Reviewed
April 10, 2020 03:04 PM

Hello HubSpot Community, 

Thank you as always for your continued feedback, it helps us build a great product.

We are constantly evaluating and re-evaluating our priorities and roadmap to deliver as much value to our customers as possible. Dependent properties are cetainly something we see a ton of value in. Based on the comments and use cases you all have listed, we are reviewing this request and its feasibility among other priorities on our roadmap. At this time I don’t have any details around timing or delivery, but thanks to the comments and votes on this post we’re actively looking into what it would take to solve this problem. 

August 30, 2019 08:08 AM

Hey HubSpot Community! Dylan from the HubSpot Product Team here.

I found this post via @ChrisHiggins ' awesome post on an INBOUND wishlist

Transparently, this isn't something you'll be seeing this year at INBOUND. However, I really appreciate all of the input and suggestions on this post thus far. "Dependent properties" as we call them, are firmly on our radar. However, we've identified a few higher-priority improvements to be made to properties before we get around to building dependent properties. 

In the coming weeks, you'll start to see a beta version of properties that will ideally set the stage for us to include "Dependent Properties" in the future. Stay tuned, this is certainly on our minds as well.


- Dylan 

227 Replies
Member | Diamond Partner

great idea

Contributeur de premier rang

Following. Hoping this feature is rolled out soon.


would like this too please.


Absoultly Im just setting up and devestated this is not a feature!!!


HubSpot Employee

It'd be great to have this feature so that users can manage their properties in a much more efficient manner


We have created some company properties to be filled out by our SDRs when they are talking to target companies. We want to gather this information to do some targetted marketing at the end. Now I was wondering if we could make some fields mandatory before a deal could be created. So to create a dependency that certain COMPANY properties need to be filled out before it's possible to create a DEAL for that company.


This is a fundamental requirement and I'm surprised that it's not supported already.  Please add my name to the list of those that would like to see this for companies, contacts and deals.


I strongly agree about the need for:

1.  making fields mandatory after initial creation

2.  conditional logic to make other fields mandatory

Key Advisor | Platinum Partner

It would be great if we could create conditional or dependent property values.


For example, I have two properties, let's call them Property A and Property B.


Property A is a drop-down with let's say 10 values.

eg. Tradeshow, Conference, etc...


Property B is a drop-down with 30 values, 10 of each are directly related to the 10 values of Property A.

Tradeshow A, Tradeshow B, Tradeshow C,  Conference A, Conference B, Conference C, etc...


Now if I select value 1 in Property A, Property B's available options drop down to the 10 that are related to Property A.


eg. Property A = Tradeshow, Property B = Lists only "Tradeshow A, Tradeshow B, Tradeshow C" as available to select.


I realize this would require a massively custom solution, and the things we as partners could provide our customers would become endless in terms of solutions and ease of use inside of the product.


Currently, our workaround is to add additional values into Property B to identify what group they belong to.

Eg. -- Tradeshow --, Tradeshow A, Tradeshow B, -- Conference --, Conference A, Conference B


Second to the above idea, it would be also helpful if based on the user's selection of value, set that property B is required. In an instance where property A does not need further macro data then we would need B to be required.


Our SDRs qualify leads and then they ask their BDMs to exclude the ones they don't want to be part of an email campaign. So what we need is something like: 

1) Select contact that BDM wants to exclude
2) Click edit and choose property "Excluded by BDM" to select yes

3) Now we want an additional field to appear where they can choose the reason why


Does this make sense?

Key Advisor



Looks like you merged my idea (and its votes) into this idea. But did you notice the idea her is more narrow than mine? It does not include mandatory / not mandatory? 


Appreciate that we do not waste an idea that brought 2+ years of comments and likes. 


Could you please make sure the sense of both ideas are in the merged one?




Would need this feature in one of our Ticket Pipeline.


I would like to enable ticket properties based on the set value in a particular property.





We have a custom lead source dropdown field to capture offline sources at a more granular level. It would be really useful in this case to have conditional logic to serve a dropdown of drill-downs based on the original source e.g. 


Original source = A

Drill-down options = 1,2,3


Original source = B

Drill-down options = 4,5,6


any info regarding this request ? 


I would also find this super helpful!


Another instance where this would be helpful is with Deals.


You can have multiple pipelines, but the properties users must populate when creating a new deal are the same across all pipelines.


Use case - different set of fields required for the following:


  • existing business pipeline (fields displayed regarding renewals / professional services)
  • new business pipeline (fields displayed to capture more detailed requirements).



I was surprised that this fundamental problem has not been resolved since 2017?


We would like to see field dependencies for company properties too.


We also have a need and see field dependencies for companie and contact properties as a useful feature.

We are especially interested in filling fields from other data sources like excel sheets (e.g. setting a price value depending on an age value - and the data exchange should work in both directions.


Part of our current case is, that a person fills a form and enters an age (or birthdate). Depending on an age we want to fill a price field - and the price values are coming from an excel or google sheet (and may change in future).

We currently built workflows as workarounds but its far a away from being a smooth solution especially because we are going to implement a secend variable next to the would be much easier to have an exchange between table values and CRM fields which includes to connect external files to the CRM and workflow builder.


This would a great feature to enable sales. The use case I need it for is when a Lead Status is changed to "Disqualified," require the property "Disqualified Reason" to be filled in by the sales rep. Sales and marketing benefit from knowing WHY a lead was disualified.