👋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.
Use case: SDR picks a lead status "Nurture", then I need them to pick a Nurture reason "Not ready to buy in 6 months", or "Missing product feature X".
Otherwise, I have no idea what nurture program the leads should go into, and "nurture" becomes a dumping ground of bad leads that the SDR's don't want to deal with.
Not having this is a huge miss that causes significant operational inefficiency and a lack of data cleanliness. Every CRM I've used has had the ability to make related fields dependent. Please prioritize this!
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!
I have used two products Salesforce and Filemaker Pro where this type of functionality is available. For use in Hubspot, we are moving a client from SF to HS and they have several fields that depend on other fields to determine the options. To work around this in HS we are flattening them into a single list and using triggers to update the individual fields. This solution does not change the field values just makes it easier to display them as two fields. This would be a great feature!! Thank you.
I'd just like to chime in here with our use case for this, as we are a SaaS company selling subscriptions to our service. We have "Close Date" and "Expected Bill Date" fields in HubSpot for our Deals. In some cases, the Expected Bill Date can be different from the Close Date, especially if the deal closes ahead of the subscription start date, and therefore the customer will not be billed/invoiced until closer to the start date of their subscription. To help with errors in our forecasting, we would like to be able to make the Expected Bill Date field be dependent upon the "Close Date". If at ant time a rep updates the Close Date field, they should be asked (by HubSpot) to update the "Expected Bill Date" field, and we should be able to specify (internally within HubSpot) that the date must be equal to or after the Close Date. We currently make these fields (Close Date and Expected Bill Date) required when creating a deal, but if the Close Date is ever updated along the way, it's easy for reps to forget to update Expected Bill Date.
Upvote! We would like to have the option to make field mandatory, if another specific field was filled in. Creating tasks via workflow is not an option, takes too much time.
Use case: The agent sets a lead-status to "not qualified". Of course, we want to know the reason why. So he/she has to fill in this field as well.
This is an absolute requirement when building out solutions. Without it we have to do an incredible amount of API work on the other side where we have integrations. This is expensive and time consuming, both developmentally and from an operations perspective.
We are currently doing a revamp of our data and structure. For starters, I am looking into updating our Region property and making it the master property. Obviously if this idea gets implemented, I'll have APAC, EMEA, US, LATAM etc on the dependent property. I will further drill it down to countries per region and so on and so forth (as applicable).
Hope this is a good use case for Hubspot team to speed things up.
This would be incredibly useful for me. Especially if you could get these relevant properties to pop up on your screen much like what occurs when you move a deal to closed won in a pipeline, a box pops up prompting you to enter the won reason.
Would this give the ability to make madatory adding of a customer to a ticket? Right now, a ticket can be created without adding a customer which is very troublesome.
Você deve ser um usuário registrado para adicionar um comentário aqui. Se você já estiver registrado, faça logon. Se você ainda não estiver registrado, registre-se e faça logon.
