We need a way to pre-set the value of a property field. I am constantly creating new Contacts where 85% of the time, the values of several properties are always the same. For example, I have a property called HaveX that should almost always be a value of 'yes', but I cannot set the default value of this (and other properties).
Hubspot Support response:
It is not currently possible to set a default value for properties within your account, as we don't have the ability to force a property to always have a value. However, you can set a default value for a property in forms by checking the "Pre Select" box next to an option in the form editor. You also have the option to create a workflow to automatically update records that don't have a value for the property in question.
my response >> I know about setting workflows and forms, but neither would fit this need. Can I ask for this to be considered for future development?
Weitere Ideen mit folgender Beschriftung anzeigen:
would save a lot of time and workflows and also it seems to be a blocker for some zapier implementation for us. This really feels like a basic feature, it's a bit weird not to have it
Particually annoying when you're creating a Deal/Ticket/Lead and you only have 1 pipeline...yet you still have to manually select the one pipeline during creation process.
(Of course, I can do this via a workflow, but I don't wanna')
Does the merging of this thread with another similar one (I received an email) suggest that this is FINALLY going to be implemented as a sorely-needed basic feature of the CRM?
+1 to this idea. We are looking for ways to boost sales rep efficiency and I have other workflows where being able to have a property take a default value it would be super useful Use Cases
*Renwal Deal Term Length - default to 12 months (there are rare cases where this isn't true but it would be great to automatically have this value set without having to create a separate workflow for it) *Deal Creation - 90%+ we ask sales reps to select the an industry and 90% of the time it's "Legal" so pre-filling that would be ideal (this is true for other properties as well) *Properties used in Calculation Properties - Calculation properties don't work if the variables used in the calculation are blank. Being able to set a default value for the properties used in the calculation properties would ensure the calculation property executes without having to write a bunch of if/then statements that get pretty complex
This functionality would be useful for our teams to save some time in pre-filling fields where 90% of the time, one value should be selected. It seems like the community is asking for this and sees this as basic functionality that's currently missing - HubSpot, is there any update on getting this added?
This seems to be basic functionality in Salesforce, but somehow has taken years for Hubspot to even consider? Definitely would save a lot of headaches and workflow bloat. I hate having to create workflows just to populate one field!
I'm Sabrina from HubSpot's product team we're looking into having Default Values as part of our roadmap. We'll keep you posted as we make progress toward this goal. In the meantime, if you are interested in participating in any research as we shape the solution, please submit your contact information in this form. Many thanks!
Fairly simple use cases become complex without this. e.g.
We have a testing company we use to test out integrations, and it generates a TON of deals which obviously skew reports.
Our solution was to use a Boolean on the Company, and a Property sync on the Deal. The problem is that by default the Boolean is Unassigned. And really no one should touch this field.
Simply defaulting this to No, allows us to use a filter reliably in Reports to exclude these.
I can use Tokens in the Create Deal Name, but that **Add Default Value** option isn't available when trying to use Tokens in the Create Ticket Form. Is there a timeline to adding this functionality? It seems if the code is built for one, it should be able to be adapted for this other object and would save a lot of time on the UX side when creating tickets. Also ensure naming uniformity company wide.
We use Tickets heavily and have customized the input forms for various ticket systems different teams use to a great degree. We should be able to set default values and placeholder text on the form fields our teams use internally same as customer-facing forms.
Sie müssen ein registrierter Benutzer sein, um hier einen Kommentar hinzuzufügen. Wenn Sie sich bereits registriert haben, melden Sie sich bitte an. Wenn Sie sich noch nicht registriert haben, führen Sie bitte eine Registrierung durch und melden Sie sich an.
