"allow_null=false" don't works (Dictionary Entry Override Attributes)

Gilmar Adrian
Tera Contributor

Hello, I'm trying to use the Dictionary Entry Override, where the Attributes were "allow_null=false" with the objective that in the choice field (State) don't appear the option "-- None --" how it's now:

GilmarAdrian_0-1722168516365.png

 

I defined this attribute to false or true, and don't works, like showed in the next screenshot:

GilmarAdrian_1-1722168631785.png

And the "-- None --" option continuous appear yet.

 

Anyway, I want to know how I can hide the "-- None --" option in the for.

 

Reference: Dictionary attributes (servicenow.com)

1 ACCEPTED SOLUTION

Mark Roethof
Tera Patron
Tera Patron

Hi there,

 

Interesting one to perhaps also raise a ServiceNow Support Case for.

 

Most attributes do work for dictionary override, though it looks like this one (with both true and false) doesn't. I also don't see any out-of-the-box dictionary overrides with this allow_null=false.

 

Kind regards,

 

Mark Roethof

Independent ServiceNow Consultant

10x ServiceNow MVP

---

 

~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field

LinkedIn

View solution in original post

5 REPLIES 5

Sohail Khilji
Kilo Patron
Kilo Patron

Hi @Gilmar Adrian ,

 

try 

SohailKhilji_0-1722169473856.png

 

or use client scritp to hide using g_form.removeOption();

 


☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....

LinkedIn - Lets Connect

Hi @Sohail Khilji

 

Thanks for your answer! But, won't be possible because the State it's an inherited field.

GilmarAdrian_0-1722170889327.png

 

About the second option: how I can retire the "-- None --"? If the intern value is null/empty? Just put '' how parameter to the removeOption() function?

 

g_form.removeOption('');

 

 

dont you see an option called ''include none''  in type specification tab ?


☑️ Please mark responses as HELPFUL or ACCEPT SOLUTION to assist future users in finding the right solution....

LinkedIn - Lets Connect

No, because it's an inherited field. For this reason that I need to use the Dictionary Override with the attributes. And I can't change the original Dictionary entry at the Task table because the impact with