Ampersand symbol not displaying properly in a reference field (Istanbul)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-14-2017 03:16 PM
I have a reference field looking to my assignment group. One of the groups has an & ampersand character in their name.
On my ticket form if I use the reference field to find the group, the name with the & symbol shows up fine. After submitting the ticket, the reference field now shows the group name with a & instead of &.
Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2017 11:58 AM
Hi Shane,
Just for your information, officially this problem is lodged in ServiceNow as Problem PRB707255 under CMDB Problem Category. Please refer this link: All other Istanbul fixes .
It is said that the issue is been fixed although I'm not sure enough. According to the KB article KB0598932, this issue is fixed in Istanbul Patch 0. Refer this link: ServiceNow KB: Istanbul Patch 0 Fixed Problems - Downloadable Spreadsheet (KB0598932) .
It would be nice, if any member from ServiceNow team confirms the same.
I hope this helps.Please mark correct/helpful based on impact
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2017 01:42 PM
I see this is for CI relations, while my field is a simple reference field. Are they related?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-15-2017 10:18 PM
Hi Shane,
I only can relate your issue description same with the mentioned one in my last response. That's why I said that it would be great if any ServiceNow team member confirms on this. In this case, just wanted to draw your attention in that.
I hope this helps.Please mark correct/helpful based on impact
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-16-2017 01:26 PM
Well we are currently on patch 2, so I think it's a separate issue.