Display Value disappeared on Reference Field

[Sue Frost]

We had a release last night and for no release that I can see, the Change request field on Change Task has lost it's display value:

The field still contains it's reference value.

Existing change tasks are impacted. New change tasks are also impacted - both those created through the workflow and manually. 

I don't see any differences in the dictionary entry for that field - there are no other fields on Change Task that are set to 'display' and the field doesn't have a dictionary override. (Change request is NOT set to display). 

I've compared the dictionary entry to our pre-release backup and there are no differences.

If this problem were

• caused by some conversion job (we had some) from the release, I'd expect new Change Tasks to be fine
• a workflow issue, I'd expect manually created Change Tasks to be fine
• a workflow issue, existing tasks should be fine but new tasks impacted

Where else can I look for root cause? I can't begin to deal with the issue until I know what's causing it.

TIA!

[Mark Roethof]

Hi there,

If you look at the xml, what is shown there? Is the displayvalue missing there? There reference itself (the sys_id to the CHG) looks to be there.

If my answer helped you in any way, please then mark it as helpful.

Kind regards,
Mark

---

LinkedIn
Community article list

[Sue Frost]

The XML shows the sys_id of the Change Request:

<change_request display_value="">66173884db7d0cd071da38fbfc96195c</change_request>

It's only the display value that's missing. Everywhere.

[Ashutosh Munot1 · Accepted solution]

HI,

Check the display value true on the table i.e. Change Request. There should be one field which should have displayvalue true.

Thanks,
Ashutosh

[Sue Frost]

THAT'S IT!

There was another field on Change Request set to display. I removed the 'display' flag and now things look better.

I will take that up with the developer.

Thanks!