👋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.
YES! Anybody who works in a non-veritcal industry needs different sets of criteria to qualify prospects of different types. We end up with tons of non-applicable fields for both contacts and companies, which could easily key off of a "type" selection.
I agree. This is functionality that is available in almost every CRM I have worked in over the past 20 years. This is much needed from the user perspective in order to maintain good user experience and adoption/usage.
Agreed. As well as the ability to create custom look-up fields. For example, on a deal, I want to be able to have a look-up field for the "Vendor sales rep" that is also a contact in HS.
This is an absolute must-have in the CRM. We have clients that want to move to Sales Pro and fully use the CRM, but this is a hang up. We need to be able to add dependent fields and set whether they are required for contacts, companies and deals. One use is case is working with channel partners. We have direct sales deals and then deals where a channel partner is involved. When a channel partner is involved, we need a dependent field that prompts the sales user to select the appropriate channel partner on the deal.
Yes! This feature would be greatly appreciated! The feature of a multi-level dropdown or multi-level checkbox is something that would be implemented in a lot of marketing AND sales scenarios and situations.
For already existing records, we need to be able to have conditional logic for properties to display/not display them and to make them mandatory/not mandatory.
Use case 1 - "State": display a property based on conditions
If US is choosen in "Country", then display a "State" field.
Use case 1 - "Unqualified reason": display and make mandatory a property based on conditions
If 'Lead Status' is "Unqualified", then display + make mandatory "UnqualifiedrReason".
Note: the solution of having values "Unqualified / {reason 1}", "Unqualified / {reason 2}" as values within the leas status property is not acceptable since it would make us lose the possibility to count "Unqualified" in reporting (as values can't be grouped).
@bfelker: for achieving what you want, go to setting then to your pipe (Small gear top right > Sales > Deals). Then "Edit properties" for contracting stage. Then pick "Contract Start Date" and make it mandatory.
Once it works, kindly remove above comment as it's not valid here.
I would find this very helpful as well. But I'd love to have the same logic for deal properties.
Use Case 4: If a contact is marked as existing business, then display dependent fields to quickly describe the relationship and previous purchase / preferences.
I have a client who is working on an integration to Microsoft Navision, but it's going to be sometime before that is realized. This would be an easy way to have the sales team import data into HubSpot piece by piece for the foreseeable future.
