Sicon Known Issues

RESOLVED | 14356 – Error when adding time to a works order: “unable to update the object as the object has been deleted”

Version Resolved In

Sicon Manufacturing v221.0.89

Version Reported In

Sicon Manufacturing v221.0.87

Detailed Description

An error occurs when saving a timesheet entry on a Works Order.  This is a specific scenario that will not impact all sites, but is worth being aware of when considering an update while Sicon investigate this known issue.

The error reads:

“Unable to update the object (Sage.Manufacturing.BusinessObjects.BillOfMaterials.BomOperationResourceDataObject, ), as the object has been deleted”

This occurs when an operation has been added manually via the Add Operation button on the Operations tab:

14356 - Error adding timesheet to WO - 1

In the above example, operations 1-9 have been pulled through from the BOM.  Booking time against these will cause no error.

If an operation has been manually added to the Works Order using the Add Operation button above, at the point of trying to save any time recorded against that operation in Sage, the timesheet error occurs:

14356 - Error adding timesheet to WO - 2

Although it is possible to close the error and a timesheet entry has been recorded, the time isn’t added to the works order and therefore it cannot be completed as the costs are not accurate.

Impact: Medium

  • Urgency | Ability to work affected; no workaround currently available.
  • Impact | All users affected, but only if using the feature as described above.

Workaround

There is no workaround available for this and Sicon are working on this as a matter of priority. If adding manual operations is part of your site’s process, we would recommend against updating to 221.0.87 or above. This is being worked on as a matter of urgency and working to have a resolution for 221.0.89 at the latest.

Development Priority Voting

Please let us know your development priority for this Known Issue by providing us with a star rating based on the below;

  1. Not causing any problems – not a priority.
  2. It’s annoying, but not causing too many problems – not a priority.
  3. Would be nice to be fixed, but not essential – not a high priority.
  4. It would be helpful to have this fixed – fairly high priority.
  5. Really needs to be fixed as soon as possible – high priority.
0 - Development Priority Level
5 0%
4 0%
3 0%
2 0%
1 0%
5
Please Share Your Feedback
How Can We Improve This Article?
Contents