HubSpot Ideas

SteveJenns

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.

 

Thanks!

Steve

HubSpotからのアップデート
ステータスに更新: In Beta
September 14, 2023 08:21 AM

👋Hi all! I'm Rachel from the Product team. An update for you  - we are now in private beta for Conditional Property Logic, a feature that will enable you to set conditional logic for enumeration properties. This logic will be triggered when users make edits to properties across the CRM - specifically, in the ‘create record’ form, on the record page, and on the index page. If a property is required, users will not be able to save their changes until the required property has been filled. This feature is available for all Hubs, Professional+ subscription. 

 

Your Customer Success Manager can request access to this beta on your behalf. We plan to move this feature to public beta in the near future based on usage and customer feedback, at which point customers will be able to opt in themselves. Thank you all for your feedback!!

May 16, 2023 08:23 AM

⚠️ UPDATE May 18, 2023: Thank you all for completing the application form! Registration for this study is now closed, as we have recruited the number of users needed for this study. We had a huge number of applications for a relatively small number of spots, and some specific internal criteria for who could take part. If you weren't able to help this round, please keep an eye out for future research studies!
 
Next, we'll conduct that research and use what we learn to build and adjust our proposed feature. Stay tuned for more updates!
 
Original post copy is below:
---
 
Hi everyone! My name is Kyle and I’m a Product Designer at HubSpot. Good to meet you!
 
Some good news: after a really informative beta period, we're working on expanding on this new feature. With these new updates you'll be able to show and require properties related to a chosen option in another field, throughout the entire HubSpot CRM. To make this work, we're trying a more centralized location for managing this logic, which means some fairly big changes to how the feature works.

Based on what I’ve been reading here, I think this would solve many of your needs. But first, we have to test it to make sure it’s easy to use and understand. That’s where you come in.
 
Would any of you be interested in participating in a paid user research study, testing conditional logic settings? In order to ensure that this feature is effective and easy-to-use, we need to test it with you, our users. That will help us understand how well it works and meets your expectations.
 
Session details:
- Participants will be paid upon completion of the session
- Session will require no more than 60 minutes of your time.
- Session will consist of a recorded Zoom call where you’ll complete tasks using a prototype of this new feature
- You’ll be asked to provide honest feedback as you go
 
👉 Interested?  Please sign up using this Google form. If you qualify, we’ll email you to set up a time to talk. Registration for this research study is now closed. Stay tuned for more updates as we learn and build!
 
Once you’ve submitted the form:
If you qualify, you’ll receive an email within the next 48 hours with the subject, “Schedule a HubSpot UX Research Session”. Just pick a time and we'll do the rest. We’re looking forward to sharing this prototype with you and gathering your feedback.

March 14, 2023 09:52 AM

Hi folks,

We have received quite a few responses for this beta. To help us better collect a list of eligible beta participants, please complete the following Conditional Logic Beta Participant Eligibility Form .  

 

Best,

Shay

February 06, 2023 07:34 AM

Hi folks,

I'm happy to report that this Idea is now In Development! Our team is actively implementing a solution for this feature.

 

Again, the product development process is always filled with unexpected bumps and hurdles, so I can't give a timeline, but I am confident in saying we'll deliver this feature as soon as possible.

 

All updates will be relayed on this thread, so stay tuned! 

 

If you are interested in being a beta participant, please send me a message. Once we're beta ready, we'll contact you with the next steps. 

 

Best,

Shay

ステータスに更新: In Planning
July 12, 2022 06:50 AM

Hi folks,

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

 

I'm happy to report that this Idea is now In Planning! Our team is actively researching and scoping out a solution for this feature.

 

The product development process is always filled with unexpected bumps and hurdles, so I can't give a timeline, but I am confident in saying we'll deliver this feature as soon as possible. If you are interested in giving feedback while we are in the research phase, please send me a message and we can set up some time to chat.

 

All updates will be relayed on this thread, so stay tuned!

 

Best,

Shay

ステータスに更新: 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!

-Shay

ステータスに更新: 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.

jeff

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.

 

jeff

ステータスに更新: 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 

312件のコメント
ステータスに更新: In Beta
rwebb1
HubSpot製品開発チーム

👋Hi all! I'm Rachel from the Product team. An update for you  - we are now in private beta for Conditional Property Logic, a feature that will enable you to set conditional logic for enumeration properties. This logic will be triggered when users make edits to properties across the CRM - specifically, in the ‘create record’ form, on the record page, and on the index page. If a property is required, users will not be able to save their changes until the required property has been filled. This feature is available for all Hubs, Professional+ subscription. 

 

Your Customer Success Manager can request access to this beta on your behalf. We plan to move this feature to public beta in the near future based on usage and customer feedback, at which point customers will be able to opt in themselves. Thank you all for your feedback!!

HKahn
参加者 | Diamond Partner
How can we enroll in this Beta please?
OMueller7
参加者

@rwebb1 Are you planning to expand this logic to be compatible with non-checkbox/radio/dropdown properties? I understand this could add quite a bit of complexity, but even just an "is known"-style condition to trigger when someone fills out a text-input property would be incredibly useful. Thanks!

lgancarz
メンバー

I second the comment above. Our need for this stems to date picker fields, which is not available in this public beta. We need reps to be forced to update required fields any time they are edited, specifically date pickers. 

chris_bridgerev
メンバー | Elite Partner

@rwebb1 Super excited about this update! Just for my reference, do you expect down the line this logic will either work alongside or replace the conditional logic built with dependent fields in forms? This is another portion (that although admittedly not the exact same) is a similar issue I often see our clients run up against. 

callie
投稿者

Hi @rwebb1 ! Just a heads up on something my team noticed this morning... not sure if intentional or not. 

 

We have a condition set up that if BANT - timeline is YES, then require field BANT - timeline (specifics)

 

Though, one work around is that if BANT - timelines is set to YES via a workflow, then BANT - timeline (specifics) is not a forced requirement. 

AJohnsson
参加者

It's great that this is being worked on, but I'm worried that it's in public beta already with the extremely limited functionality that's implemented. We need to be able to add AND/OR functions, and have conditions other than "Equal to". I need to be able to choose "If Property A is known, then make Property B a dependant field", and I need to be able to make Property X required if BOTH Property Y AND Property Z are populated. I understand it's still only in beta, but the way it's currently implemented with only being able to choose "equal to" and only being able to choose a single field value, and with no AND/OR, doesn't make any sense.

 

And of course, like others have mentioned, all field types need to be supported.

CFarmer7
メンバー

I'd like it if every time I engaged with a property that had conditional logic it would open the dependent properties window for viewing even if the controlling property had been previously filled out and saved. A way for my users to easily access the Dependent properties without having to edit the controlling property would really help our users workflow in our custom objects.

THalfast
参加者

I agree with the others that have said having the conditional logic check for only being "equal to" is very limiting.  It's a great start but should mimic the behaviors of the other logical checks you have already available in workflows, reports, etc.  i.e. "is known", 'is any of....[multi-select] value", and other options would be more along the lines of what I would need for my use-case.

 

For instance, if my users populate X-field (regardless of value) require that Y-field is populated.

SHinojosa3
投稿者

We are happy that this was finally implemented. One of the first couple of things that I notice with it is that we are unable to apply the dependent logic to all values in a certain property. We would like to choose an event, and then choose whether they were invitied, registered, attended or a no show. Unfortunately, we have to create a new logic for each value under this property. This leads to the next issue which is that we cannot pace these logics into folders to help keep them organized. The dependent logic need to be more visible after selecting the controlling property, you have to look for the arrow and pull up the dependent property. The UX needs a little work. 

qadfgdrtgsvfsad
メンバー

I'm using the public beta. Why is it not possible to write a condition based on Lifecycle Stage? If that property is essential to managing contact/company status, why can't we use that?

ivo
参加者

Just in case this is not in beta anymore! 🎉