Invalid update
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2014 09:54 PM
A user in our Production instance was attempting to load a new Change, and whilst updating all the relevant fields on the form, the user accidentally entered information into a field which isn't used. The field was Related Service Request (note - this Service Catalogue module is not live yet). When information was entered, the following error occurred:
"Match not found, reset to Original" and at the top of the form an "Invalid update" message.
Once this error occurred, the user removed the invalid information entered into the Related Service Request field, however the Change form exited without saving the record.
This has now occurred for a number of other users that have inserted information into other unused fields.
Note - we are currently on the Dublin release.
Any ideas from the community or suggestions to prevent records being lost due to "Invalid update" message?
Thank you!
- Labels:
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-18-2014 12:50 AM
check for 'current.setAbortAction(true)' in the business rules on the related tables....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2014 08:52 PM
I checked the Scripts / Policy Business Rules.
I searched for text containing current.setAbortAction(true) and then did a Show Matching on Change Request [change_request].
It returned 4 business rules, however they don't appear to be related.
Any other ideas please?
Note - we have just upgraded our Dev instance to Eureka Patch 5, so we will attempt to replicate the issue.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-20-2014 09:20 PM
Hello Joe,
Normally this issue is seen when setting the reference field with a value which does not exist in the refering table.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-21-2014 01:32 AM
yes in indeed . setting a invalid value to the reference field could also cause the error ... check that too .. if that dint help , I request you to put some addInfoMessage in the business rules you have found, so that we can rule that out completely.