You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Be able, for every choice/reference field, to join the display_value associated. Currently we do this for a few fields in existing models, such as for the priority, urgency, impact, task state fields in task_enhanced. We want to explore if it's possible in our package to extend this in a scalable, automated way.
There's 2 fields types: choice and reference
So every time an admin adds a new field, that metadata gets added to sys_dictionary or a similar table Choice is straightforward bc always has a display value Reference is more challenging because you have to go down a tree (sometimes the display_value is attached to the field, but if not then look to the id field, if not then look to another table references, so on and so forth). There is an engineer on our end who's done some work on the traversing the hierarchies so that will be a good resource.
End goal: The package has the ability dynamically add display values.
Another callout from customer: The table API in ServiceNow - you can add a parameter and get the display value, but it's only point in time. If that record changes afterwards, the display value won't get updated. So we'll want to take address this as well.
How would you implement this feature?
See above
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Yes.
Yes, but I will need assistance.
No.
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing feature request for this?
Describe the Feature
Be able, for every choice/reference field, to join the
display_value
associated. Currently we do this for a few fields in existing models, such as for thepriority, urgency, impact, task state
fields in task_enhanced. We want to explore if it's possible in our package to extend this in a scalable, automated way.There's 2 fields types: choice and reference
So every time an admin adds a new field, that metadata gets added to sys_dictionary or a similar table
Choice is straightforward bc always has a display value
Reference is more challenging because you have to go down a tree (sometimes the display_value is attached to the field, but if not then look to the id field, if not then look to another table references, so on and so forth). There is an engineer on our end who's done some work on the traversing the hierarchies so that will be a good resource.
End goal: The package has the ability dynamically add display values.
Another callout from customer: The table API in ServiceNow - you can add a parameter and get the display value, but it's only point in time. If that record changes afterwards, the display value won't get updated. So we'll want to take address this as well.
How would you implement this feature?
See above
Describe alternatives you've considered
No response
Are you interested in contributing this feature?
Anything else?
No response
The text was updated successfully, but these errors were encountered: