It woudl be extremely helpful if you could have dependent properties. So if a certian field in a proeprty is selected there is the option of another relaetd property showing or appearing below. This would mean that my team is only filling in relevant information and guides them for what they need to fill in. It would also avoid there being a list of lots of properties that aren't relvant.
I use workflows to assign tasks reminding the user to complete the dependent fields but having the property appear based on answer would be better real time CRM maintenance.
I support this and in some locations of HS it already exists. The obvious one would be contact or company creation. The records can not be entered if certain properties are not completed in the prompt.
I would like to see something like this on value - level. For instance if a value is "disqualified" then another property would be prompted for completion that could be "DQ reason".
I reckon this feature is incredibly crucial and downright indispensable. Both Zoho and Salesforce offer it. We've got a number of clients itching for this functionality, and there's one in particular for whom it's an absolute must-have. He might end up choosing Zoho, even if Hubspot suits his needs more efficiently.
I can't beleive that this doesn't have more upvotes! This is a basic CRM maintenance topic. Why does it take HubSpot so long to take notice of this functionality!
This seems like a basic function of a CRM...please add! We need this in so many different places when a certain property changes - we have so many dependent properties in both contacts and companies.
@jaah this is good but this is another thing. What I would look for is: Closed lost reason = other, FORCE me another property to be filled, called : Other Lost Reason (Detailed)
I realize we now have "dependent properties" as options in propeties, but it would be helpful if once the property was set as dependent it only showed when chosen and then stays if filled in.
ex: do you have dog> yes, no Then if chosen yes> what breed is your dog.
The way dependent properties were built is that I can add the dependency that if I chose yes, the field for what breed does display, but once filled in, it disappears. I want it to show on my default view, only if the dependent field is filled in.
Adding my voice here: My expectation for a dependent property aligns with SKonkin, as noted above.
I want to be able to more efficiently label my support tickets. "How To" and "General Inquiry" aren't specific enough. I want to break these out and have my team break these out as they fill out the ticket so we can do better deep dives on where in our product we need to make adjustments.
Right now, I can build out multiple ticket fields with the various amount of options to have the team try to remember and decipher what to choose, instead of giving them a nice controlled amount of subcategories related to the category chosen only. Or, I can audit my one category of "How To" in spreadsheet **bleep**.
Hubspot, please add this!!!
//edit: I need to amend my comment. I found what I needed through Conditional Property Logic!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
