- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2024 07:10 AM
Recently one of our instances started exhibiting this strange behaviour where newline characters are doubled in journal fields. Here's the same journal entry presented in the faulty environment and a functioning environment:
versus:
This appears to affect all Journal List objects across multiple tables (Incidents, Requests, custom task-extending tables). I've tried searching for all system properties containing the word 'journal' but the values are the same across both the faulty and functioning environments.
Anyone have any ideas as to what might be causing this?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2024 05:18 AM
In case anyone is curious, this issue went away when we upgraded to Washington Patch 7a from an earlier version of Washington.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2024 08:01 AM
Have you viewed the records on the sys_journal_field table to see if the Value contains extra lines? Is this happening in multiple/all journal fields - Additional comments, Work notes,...? Have you checked for any Business Rules or Client Scripts that could be altering these fields or the sys_journal_field table records?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-09-2024 08:06 AM
Hi Brad,
The value shouldn't have extra lines, since the same record in the other environment has no extra lines. I checked the table anyways though to confirm and there aren't any. I suspect this is a client-side issue:
It is occurring with all journal lists in that environment (work notes, additional comments, and even some custom fields from other tables). I haven't checked any business rules or client scripts, but I'll check the latter now. Thanks for the recommendation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-19-2024 05:18 AM
In case anyone is curious, this issue went away when we upgraded to Washington Patch 7a from an earlier version of Washington.