Is there a "data lookup repository" to use as reference data?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago - last edited 4 weeks ago
I am aware of the Choice Data type and that the choice data use the sys_choice form.
However, a recent directive from our Solutions Architects have prevented us from using the Choice Data Type for anything that isn't considered as a "core" field.
We have several choice fields that are related to each other and are determined by categorization. Normally we would rely on choice data with dependent fields but as mentioned earlier we are forbidden from using Choice Lists. This means that the only option is to use a reference on a customized form.
However, we are also limited to using customized forms and have been requested to use an existing repository form to hold this "choice" data as a reference. Does such a form exist?
(Note: this kind of form would be used closely with HRSD, so something related to that would be appreciated)
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
purely subjective requirements, have the Solutions Architects design what they want.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
They are asking me to use an existing form that would suffice as such a repository. Apparently there are licensing concerns that would preclude creating a new table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 weeks ago
I guess you need a Reference field to a record in the sys_choice table. The 'repository' it seems is the sys_choice table.
but you post you can't use 'Choice lists'. Then use an 'onChange' client script to enforce allowed values, or a Business rule to enforce allowed values for a field. Hard-code the values if not stored in some table.
Seems your Solution Architects aren't up to the job designing a solution for their ask.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The reason we cannot use the sys_choice form is because it is locked down by our platform owners. There is an audit going on with ServiceNow given that there are so many unused and invalid choice entries to the point that it is causing some instability on ServiceNow.
The reason we also cannot create our own form to do this is because we have hit our upper limit in customizable tables per our license. So we are trying to figure out what we can do in the meantime.
This is not a situation I appreciate being in.
