👋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.
Dear Hubspot Team, we also need this function. One use case: When i set the property Lead Status to "unqualified", I want to know, why the lead is unqualified. Sales should only fill out the reason in another property when the Lead Status is set on "unqualifed"
Up voting please. Use case 5: A client wants to add a field to companies to set the risk of non-renewal. They want a dependent field only if the risk is high. They use Marketing Pro and Sales Pro.
We have an extremely negative impact on our process, which could be avoided if we had this in HubSpot
We currently have to fill in several additional fields because we don't have this functionality. As the calculations depend on filling all the properties to be executed, we always have to fill all the properties.
In my company, we are experiencing a huge loss of productivity.
We could really use this for our sales/marketing pipelines. If we have a data field completed by a customer, it would be helpful if we were able to then have other fields updated based on that one. For example, when someone completes a form with the field 'country', it seems redundant to ask them 'region' too. As a global financial company, we actually need both fields. Without this feature, we have to ask them both, when we would prefer to map countries they provide, to specific regions that autofill.
Conditional fields are a must (in my book) to creating a streamlined CRM that doesn't make end-users feel overwhelmed with the amount of properties on an object.
For example:
Company has X vendor that happens to be a partner solution. Due to the partnership, end-user needs to input if X vendor solution was a result of the partnership or a direct relationship that was established separately. If company has 4 partner solutions, it equates to 4 corresponding properties.
When the properties have no value, the subsequent property regarding the "source" of the client's vendor solutions is not needed. The ability to make sections conditional based on lifecycle stage is a great start and demonstrates that conditional properties are possible...would love to gain insight as to why this wasn't made available for custom properties or at the very least, more than 8 properties.
We want to create an unqualified reason field that is a dependency on lead status. Without the ability to create dependent fields, it makes it tricky for us to enforce data standards across the org.
We would like to have dependent fields required as well. We are using forms for customer set up, and if they are a new customer, we would like specific documents to be required. It would be very helpful and more efficient - so we don't have to go back to the sales person entering the data if they miss it.
Currently, we are trying to implement the HubSpot CRM to a global team, but restrict a lot of function of ownership changing as well as subscription updates for admins only; this is a perfect use case where a dependent property would be SUPER helpful, as data validation is required for some sibling properties in the ERP/former CRM system.
As a HubSpot Partner, we need this for almost all of our clients. We especially need it for those whom we're migrating from Salesforce to HubSpot. If they have these rules set up in Salesforce--that their sales team has already been trained on--imagine trying to position HubSpot as a better fit than Salesforce while losing this functionality.
I would love to have this feature! I'd rather have it as a field dependency for Deal Properties, but the field dependency would be great either way.
We want to be able to allow our sales and marketing team to choose "other" within multiple properties, for example, "deal lost reason." Then, once they select "other" I'd like to be able to require them to enter the other reason in a separate field. As you can see, I can't simply make the "other reason" field mandatory. But, with my current setup, few users actually go back and enter the reason.
Been tracking with this and see it's been going without a solution since Apr 15, 2017
I would love to see a dynamic dropdown list that only displays the desired options based on the previous fields selection.
Creating separate properties to do this is really complex and unhelpful when it comes time to filter based on particular selections if they are in different properties.
PLEASE add this feature. It would really help us cut down on bad data coming in.
For example, we request customer vehicle information. In order to get this we need: Year, Make, Model, Engine.
We currently only have "Make" as a dropdown list while "Model" and "Engine" are open fields. The problem is we get vehicles input all kinds of incorrect ways. For example: F-250, F250, F 250, 250, etc...
If I make the Model field a dropdown, it would contain over 100 options, where I should only be displaying maybe 5. This makes it confusing to the user, not to mention it opens it up for all kinds of wrong entries. Having this data clean is very important to us, otherwise it is useless.
This is essential for our support team to function efficiently. We previously used Desk and Salesforce in which both offered this functionality. As our company continues to scale and grow, this is becoming more of a need. Our drop-down list for custom properties now have more than 100 options to choose from. This is incredibly inefficient and is asking for tickets to be categorized inappropriately and thus effects the accuracy of our reporting.
