Field randomly clearing on Save
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2014 08:56 AM
Version: Dublin Patch 3
Table: u_case_task
Extends: u_case
Extends: Task
Field: u_authority_level on Table u_case and inherited on u_case_task
When I hit New Case Task and populate the u_authority_level field and hit save approximately 75% of the time the field is cleared. The field is not cleared immediately as it is used to add a Skill to the Case and that happens successfully. This only started happening after we upgraded to Patch 3. Our instance that is not patched yet does not have this issue.
I have gone so far as disabling every Business Rule, Client Script, UI Policy, Script include that touches the Case Task table and the issue persists. If anyone has some ideas of things to look at or things to do I would be interested in a different perspective!
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2014 10:55 AM
Hi Jim,
Thanks for the response. I took a look because I have definitely experienced what you describe, but in this case the field is only displayed once.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2015 01:53 AM
Was this ever resolved? We are seeing the same thing on Fuji P3 on the incident form with a field we have added as a drop-down list. The value is filled in, form saved, value disappears (not in xml and if form re-loaded value still not there), re-enter value and save again, value stays put.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2015 08:59 AM
Unfortunately the fix was deleting the field and creating a new one.
Very odd bug
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2015 09:27 AM
OK, thanks Paul. SN are investigating but can't trace what is causing it. It has now been referred to their developers. We also have a similar problem with the Impact/Urgency combination - if 1 is set for both, urgency goes back to the default of 3 on the first save but stays put if reselected and resaved.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-13-2017 04:32 PM
Hi Paul,
I know this is a very old post, but i would like to know if you got this issue fixed? I am running into this issue and we are running on Helsinki Patch 8. I created a new table and had 3 new fields. When I populate these fields and save it, all the fields get emptied out and when i re-enter and save, it stays on. I have tried deleting the fields and creating new ones and then ONE field started to stay while the other two just disappears. I checked the XML as well as mentioned above and there is no value for the two fields emptying. Please do advice me if you have figured this issue out or got a work around.
Thank you!