- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2022 12:18 PM
I have a dropdown with choices, and have configured it for Dropdown with --None--. I want to make it mandatory to select a choice, but not have --None-- considered as a choice. However, the dropdown is showing a choice and not --None--.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2022 01:52 PM
Hello,
And just to clarify, you're going to a brand new record and don't see the "-- None -- " option by default in that field and instead, it's displaying a selection?
Or are you going to an already created record? Because if so, that default value would have been saved long ago.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2022 02:13 PM
Good one. I was working off an already created record. If I create a new record (case), it does default to -- None --. But, when I commit this to our production instance, all currently opened records/cases won't show -- None -- as the default?
Also, I want this to be a mandatory field/choice. I have a UI Policy that is configured to show this dropdown field (Refer to Partner Account) if a specific choice is selected in another dropdown field (Close code). When I go to the Dictionary for the Refer to Partner Account field, Mandatory is greyed out.
When I look at the UI Policy Action, Mandatory is also greyed out.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2022 04:14 PM
Hello,
Any record that has been saved already, where you had the default value there, will not go back to "None", automatically, because it's already been saved with a record.
Going forward, new records, will start with None.
As far as the mandatory issue you're seeing, that would be something you all set within your instance. Please speak to your peers about this or perhaps look right-click the Mandatory label on the dictionary record for that field and go one step deeper to that Mandatory's field dictionary settings and see if it's possibly set to read-only.
As far as the UI Policy, that is probably also clicking that from being set due to either the dictionary record for "Mandatory" being read-only...or someone is blocking "write" privileges through an ACL.
That's sort of secondary to what your question was about here (about the None scenario).
Hopefully that sets you on the right track and I'm glad you understand how the None option would work going forward 🙂
Please mark reply as Helpful/Correct, if applicable.
Please also review other replies here in this thread and mark any as Helpful, if they were, along the way.
Take care! 🙂
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2024 11:31 PM
I have a mandatory field xyz as type choice which is configured with Dropdown with none, But list view is displaying --None instead of blank. Please suggest