Reference field is not displaying choices or saving

shawnbaar
Giga Expert

Good morning,

I have some reference fields that are allowing the user to enter text into them but do not bring up the reference list or save whatever is entered in the field.  I have checked my Business Rules and ACLs.  I do not see anything preventing these fields from saving changes, does anyone have any suggestions on where to look next?  It is only happening on the Change form for the Assignment Group and Work Notes.  Those fields work on the other Task related forms so it must be isolated to the Change configurations.  I would have thought it was an ACL since the user can type in the field, just not save any of the values.  However the only ACLs for the Change Request table are to allow itil users the ability to create and write.  Any guidance would be appreciated.

 

Thanks,

Shawn

1 ACCEPTED SOLUTION

shawnbaar
Giga Expert

Good afternoon folks,

It turns out it was a UI policy with a small typo that was throwing an error and not allowing the form to complete loading.  After turning on the developer tools in the browser, I was able to track down the UI policy and the line of code that broke it.  It was odd because the only fields affected were reference qualified fields and the journal fields, otherwise the form looked completely normal.  Since they were editable during manual testing and we were able to save the form, it did not appear as though anything were wrong.  I appreciate your assistance efforts as both of you suggested items I checked.

 

Thanks again,

Shawn

View solution in original post

4 REPLIES 4

Mark Stanger
Giga Sage

Check the dictionary entries and dictionary overrides for those fields.  Make sure you haven't got something else set as the display attribute somewhere.

SanjivMeher
Kilo Patron
Kilo Patron

Are you as an admin able to see the list when you type the group name? Worknotes anyway is a text field.


Please mark this response as correct or helpful if it assisted you with your question.

shawnbaar
Giga Expert

Good afternoon folks,

It turns out it was a UI policy with a small typo that was throwing an error and not allowing the form to complete loading.  After turning on the developer tools in the browser, I was able to track down the UI policy and the line of code that broke it.  It was odd because the only fields affected were reference qualified fields and the journal fields, otherwise the form looked completely normal.  Since they were editable during manual testing and we were able to save the form, it did not appear as though anything were wrong.  I appreciate your assistance efforts as both of you suggested items I checked.

 

Thanks again,

Shawn

Hey Shawn,

Please mark your response as the correct answer so that people know this one has been taken care of.  Thanks!