👋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.
I'd love this functionality on the deal level. The use case we have in mind is around deal source. Ideally, I would like to do two different fields for primary and secondary source. The primary source would be sometihing like partner, marketing, sales, etc. and the secondary would be a drill down based on the answer to the primary source. Ex. Primary source is partner, secondary source would be a list of partners to select from. This will greatly improve our ability to do direct revenue attribution.
Honestly, this is something that prevents people from using HubSpot as a CRM tool and choose platforms like Salesforce. This should be done and quickly.
Agreed, we desperately need this functionality to support the ability to timestamp as a lead prgresses through each stge of our deal pipeline. Currently, when the sales team create a new deal, they are being presented with a long list of date fields for every deal stage meaning the room for error is high if they choose the wrong one. If this list of date fields could be filtered to only show the relevant one according to the deal stage that has been selected, it would be a HUGE improvement.
Totally agree with @Prakhar, our use case is very similar to one of theirs.
On our contact records we have implemented a deletion request field for the sales team to select if the contact needs to be removed from our CRM. They also need to complete a 'deletion reason' so we understand why it's being removed.
To ensure that this second 'deletion reason' field is completed we'd like it to be conditional on the population of the first field - and required before the record can be saved. So if the deletion request field is set to 'yes', the record can only be saved if they have populated the 'deletion reason' field.
This functionality would greatly increase the consistency of data input for our team.
Not sure if it falls directly in line with this idea, but I'd like to be able to require that certain teams complete required fields when adding contacts that may not apply to all of my teams adding contacts. For example, when sales is adding contacts to a deal, we need to have the billing and shipping addresses completed. However, if my technical support team is adding a support contact, those fields don't need to be required as those contacts would not be creating orders or associated with deals.
This functionality would also be helpful in the ticketing side of things. For instance, having different resolution options based on the category of ticket.
@jeffvincent - Are there fundamental issues and/or architecture limitations creating this funtionallity? Backlogging this for 5 years concerns me that there are other factors besides "time".
Yes please. We NEED this - like yesterday. When on-boarding new users, this comes up ALL THE TIME and it's difficult to explain why the CRM doesn't readily support this - especially to Executive leaders.
To be clear, this is needed for properties at large; not just on the Contact object. Deals, Tickets, Companies, and even Custom Objects needthis functionality.
This would be great! I'm able to do this in forms, but it would be great to have the same option for records. In forms, I have a field called "Company Country" and if they fill out "Australia", then another field comes up with a dropdown of all the Australian states that they can select from. Love that capability.
