👋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!!
⚠️ 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.
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.
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!
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!
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.
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.
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.
Completely agree with this! When there is a long list of fields within a property, it becomes overwhelming for the team especially if thet don't NEED to see all of them.
My team wants to use this feature for tickets. We use tickets for our support function, and we were hoping to use field dependencies to help the team quickly navigate to the right field for that ticket property in the heat of the moment. For example one of our ticket properties is called "support category" and we would like our team to click on which category they think the ticket issue is in like "payments" then if they clicked payments, a list of dependent fields show up like "reports & payouts" so they can narrow down easily.
We also see use for this at a deal level with the deal stage required properties (those properties that pop up when you drag a deal from one stage to another) At the moment it seems that it isn't possible to have different properties show on that pop up for different teams or users in Hubspot. We think it would be SUPER helpful to have dependent properties showing on this pop up, so people only see what they NEED to see.
This feature actually has sooo many amazing use cases, I could go on and on! But these are our top 2 use cases that we would be SO EXCITED to implement.
I think it will be really great and exciting if we can have Dependent Fields under Ticket Properties as well. I think this is really important if we have a lot of of categories/issue categories that we need the agent to quickly navigate to.
We'd like to see this implemented too. One of our use cases is for our sales team to tag companies with vendor categories and sub categories. i.e. if a certain vendor category is chosen, display a certain set of sub-categories.
As a Hubspot Partner, I am working with a client who considers this to be mission critical.
The have four business units (and growing), and see the need to reduce the number of properties displayed to Sales People when creating contacts/enterting deal values.
My client is also aware that this can be done in Gravity Forms, Salesforce, Sugar CRM, and even quite simply in Excel – therefore making this a painful request to say "no" to.
Would love to see this implemented for Company and Deal properties as well! If we could backfill this data seamlessly too, even better. We'll be collecting the below data either way, just in a roundabout manner until something like this is created. Would save us a world of effort if this was available now.
Our use case:
We want two fields for Closed Lost Reason on the Deal level:
1. A general Closed Lost Reason (i.e. Pricing, Missing Features, Unqualified, etc.)
2. A specific Closed Lost Reason with variable field options based on the above selection (i.e. Pricing - Too High; Missing Features - Analytics, Social Integration, etc; Unqualified - No Budget, No Authority, etc.)
So the input options in #2 would vary based on what is selected for #1. The way we'll get around this in the meantime is created individual Specific properties for each general Closed Lost Reason. It'll work, but not ideal.
It would be very efficient if HubSpot could apply the same logic seen in the dependent fields used in forms to record cards. When selecting the view for a record card, it would be great if we could use logic such as 'display lifecycle stage if marketing contact status is marketing contact', etc.
In Salesforce CRM you're able to define 'controlling' and 'dependent' fields in order to manage the selection of values between two fields that are related to one another i.e. Region and Country. If I select the region 'EMEA', then I need the 'Country' field to only display values relevant to EMEA (France, Germany etc) not countries in APAC for example.
This capablility to link field behaviour to one another is usually used with Check boxes, Single select drop downs and Multi-select drop downs.
This features ensures users only select relevant values in fields/properties and therefore aids data cleanliness and reporting. Please can we have this in HubSpot too.
We also need this functionality. Specifically, we have created a Company property called Sales Stage as a dropdown select. If t the Sales Stage is Inactive or Lost Customer, we need a dependant field to appear with the reason why the customer left or is no longer active.
Great idea. Lets also add field validation = make it possible to setup "rules" on each property so that input will be denied if the rules are not met.
Example: the team tries to insert a "150" in a number-field, but the number-field "rules" are set to minimum 4 digits. So the team member would get a feedback that the input didn't meet the requirements and could therefor notice the error he or she did. The rules would be set on the field property setting, and make it possible to achive a much higher level of quality-control of all the data inputs. If the validation rules are tricky to do, you could at least add the possibility to show a warning-message on input-error, so crm users have a chance to notice their input-mistakes.
