Adding None to a choice field but not on other tables that share this choice field

[shill]

I have extended task for a custom table and need to use the contact type field from task.
The issue I have is that I have a requirement on the new table that this be a required field with a "-- None --" option as the default value so that a user is forced to chose another option.

What would be the best way to approach this without adding -- None -- to all other tasks that use this choice field?

My only thought is to create onLoad client scripts on the other forms to hide this choice which I don't particularly like.

[shill]

Well, I just answered by own question...

Come to find out, if you override the default value and leave it blank, the choice list on that table will display none regardless of the dictionary setting.
I can then make it mandatory via a UI policy.

[Shawn Dowler]

Does this still work? I could not make this happen. I had to use a Client Script on the other tables' forms to hide --None-- on load. It works, but it's not an elegant solution.

[Community Alums]

Same here. Had to use a Client Script

function onLoad() {   
	g_form.removeOption('state', '', '');
}

and a Data Policy setting the State as mandatory just to be sure.

[shill]

I think you may be trying to do something different than ignore a default value on other child table records.

In my case, the base Task table had a default of 'phone' set for contact_type, so any display of that field on any other task table would also default to 'phone' on load.

This was the intent, specifically for incidents where this is mainly used.

I needed it to NOT default to the 'phone' value and show (--None--) on a different task type.  I was not trying to remove none, but to default to it outside of the parent dictionary default value.

My solution still works for its intended purpose.