search cancel

Clarity: XOG-2015 This timesheet cannot be saved because it has since been updated by another user


Article ID: 50334


Updated On:


Clarity PPM SaaS Clarity PPM On Premise



In order to perform a test, I need 2000 timesheets in posted status. I attempted to create new timesheets using the XOG feature to quickly load data into my test system. However, when I attempt to do this I am getting an error message and I am not sure what all the rules are for performing the XOG write action.

Here is what I have done so far in preparation to use prj_timeperiods_write.xml

  1. For this I have setup a project, added about 1200 resources to the project and assigned them to a task between January 01, 2011 to April 01, 2011.

  2. All the resources are opened for time entry and project is also open for time entry.

  3. I logged in as a resource (say abc )submitted timesheet for January 01, 2011and January 02, 2011, approved and posted the timesheet.

  4. Xogged out the timesheet created in step 3.

  5. Changed the resourceID (say xyz ) in the xml file.

  6. Edited the xml file to match the attributes in prj_timeperiods_write and attempted to xog it in, to create the timesheet for the user xyz.

  7. Results error message
    XOG-2015: This timesheet can not be saved because it has since been updated by another user. Save your changes in a new file, then retrieve the same timesheet again and re-enter your time.


The current XML Open Gateway (XOG) functionality for Timesheets is not designed to move timesheet data across different systems. It is designed to bring Offline Timesheet data into one Clarity system. The scenario described above is a use-case attempting to create more timesheets in the same system; therefore the XOG action can be accomplished without this error if performed correctly. To utilize this functionality properly be sure the check the following:

  1. To create a new timesheet through XOG, perform a XOG read action to first export timesheets for the period/resource combination you are interested in with the appropriate header argument set in the prj_timeperiods_write.xml

  2. When writing the timesheet data back into Clarity you have to obey the rules with the version attribute. Observe the prtimesheet.prversion value for your timesheet before you XOG it out and after. Compare this value with your XOG file and see if it has incremented to indicate the 'version' you may write back as.

  3. If a user updates the timesheet in the application, this will further advance the version, so that when the XOG write action occurs the XOG may generate the XOG-2015 message.

  4. There are some additional rules regarding the status of the timesheet that may prevent you from performing the XOG write action, but for un-submitted timesheets this should not be a factor.

Keywords: CLARITYKB, how-to, configuration.


Release: ESPCLA99000-12.1-Clarity-Extended Support Plus