I have a custom property as a dropdown select which now it's binary (we don't know if it will handle other values in the future, so that's why it's a dropdown instead of a checkbox or a radio button). I only want to handle one of those two values: YES or NO. No empty values, no both values. The fallback should stay on NO, but I can't find (if it exists) a "default" value to this kind of selector. There's a setup window for this that I've missed?
BTW, the companies should come from API, form, tracked email.... I can control it via API, of course, but I need to control the other two sources
It sounds like you're trying to ensure that a custom dropdown select property in your system always has a value, either "YES" or "NO," with "NO" as the default value. However, you want to make sure that this property always gets a value, whether it's populated from an API, a form, or a tracked email.
Here are some steps you could take:
Set Default Value: While some systems might have a built-in "default" value for dropdown properties, it's not always the case. If there's no such option in your system, you'll need to handle this programmatically.
API Data Handling: When you're setting values through the API, make sure you explicitly provide a value of "YES" or "NO" for this property. If you don't specify a value, you could set it to "NO" by default in your API call.
Form Submissions: If you're collecting data through a form, ensure that the dropdown field is required and set a default value of "NO." If your form-building tool allows for this, you can pre-select "NO" as the default option.
Tracked Emails: If you're dealing with tracked emails that contain links, consider using query parameters to specify the property value. This way, you can ensure that the link always provides either "YES" or "NO" as the value.
Data Validation: Implement data validation on the server side to ensure that whenever data is received, it either has "YES" or "NO" as the value for this property. If the property is missing, you can default it to "NO."
Regular Data Checks: Implement a regular data check or cleanup process that scans through your data and ensures that this specific property is always populated with either "YES" or "NO."
While a built-in "default" option might not exist in your system's dropdown property setup, taking these steps should help you ensure that the property always has a value and defaults to "NO" when not explicitly set. It's important to ensure consistent data handling across all sources to maintain accuracy in your system.
We are having the same issue. I have a calculating property that sums a series of deal properites. However, the calculating property itself won't work if any of the deal properties included in the calculation is blank (not yet completed). Each of the deal properties included in the calculating property must have a value of zero or greater. This is a problem becuase those deal properties are completed sequentially and the user won't be completing the later sequence properties until months into the deal/project. To make this work, I understand we will need to create a workflow to populate the deal properties with the value of zero so that the calculating field will work from the start of the project (Deal).
We should not have to do this through workflows. This is especially the case for Number fields that are being used for calculating other fields. Since Calculation fields break if any of their calculated fields are empty, being able to set these Number fields to 0 as a default value would allow these fields to be used to Calculate values.
This feels like a no brainer as a feature given the importance of data governance to a functional and effective CRM system.
We have a check box field against a deal record which tends to have lower compliance in terms of completions, so when running reports we have a high volume of blanks. Whilst we can solve for this with making the field mandatory upon deal creation, or creating a workflow, default values would make life easier across the board.
Hey, @GTahernia👋 Thank you for your comment. I agree this would be a useful addition.
If you have a moment, can you add your use case and comment to this Idea post—Pre-set Default Property Value, please? It is making the same feature request as described in this thread and in your comment. I added my upvote as well.
Another way (but more difficult to pull off) is to create a custom app and tell it to listen to a webhook on whatever object you're working with. When it receives an event, it can set the default value of that property.
So if you're working with a deal:
Create Deal -> App receives webhook event -> App reads the deal -> App sets the deal property if it not set
There isn't any way to set a default value at the property definition level. You can set a default value for a property in forms, and you could create a workflow to automatically update records that don't have a value for the property in question, but otherwise it's not possible to force a property to always have a value.