Get Started
Support Home

We’ve launched a new Help Center!

Visit the new Documentation space for Azure DevOps, monday.com, and Jira. Or, if you require any assistance or have any questions, please visit the new Customer Support Portal for Azure DevOps, monday.com and Jira.

Learn more

Work Log ID keeps changing

Officially Answered
Follow
New post
Avatar
Mike Whalen

We are building an integration that syncs the work log data with a backend financial system. It is critical that we be able to handle creates and updates in this integration but we are running into a few challenges. 

The biggest one right now is that the ID for a work log entry seems to change after the entry is updated. Our expectation is that a work log entry would get an ID when it is first created and then never change during the life of the work log entry but this is not the case. Since the ID changes, we have no way to correlate the entry in our other system once it is updated and thus we end up with duplicates and solution that is not viable. 

This appears to be the case with RowID in the version 2.1 API with grouping turned off and also with the id field in the 3.0-preview API.

Is there are a reason that system is designed like this? How do we uniquely identify a work log entry if the ID is always changing? 

0

Comments

5 comments

Sort by Date Votes
  • Avatar
    dev
    Hello Mike,

    Could you please provide any examples of what API requests do you use to make ID changed and how do you check that ID was changed? Please share API calls and json results.

    Alexander
    0
    Comment actions Permalink
  • Avatar
    Mike Whalen

    Hi Alexander,

    I am not having the same issue today. The IDs now see to be persisting. Yesterday, I ran multiple tests using different time entries and all of them were being assigned a new ID after making any type of update.

    I assume that your API team may have identified this issue and resolved it. If I encounter the problem again, I will post the API calls and JSON data.

     

    Thanks Alexander!

     

     

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    Hi Mike!

    We haven't touched anything in API IDs in the latest releases. IDs should be persistent per Worklogs or per the same array of worklogs (if grouped).

    Could it be that you've changed the array of worklogs (groups) -> RowID has been changed?

    Regards,

    Andarth

    0
    Comment actions Permalink
  • Avatar
    Mike Whalen

    Hi Andarth,

    I did have an issue where I was grouping the work logs and thus the ID was changing when I did not want it to. However, I am 99% positive that even with the grouping turned off, I was still seeing the IDs change while using Postman with the 2.1 and 3.0-preview APIs. The 3.0 does not group from what I can tell, correct? 

    Just for reference, here are the 2 API calls I was making:

    2.1 - https://bitwizards-devops.timehub.7pace.com/api/odata/TimeExport(StartDate='2019-05-17',EndDate='2019-05-17',PopulateTopParentColumns=true,GroupTimeByDateByUser=false,IncludeBillable=true)?api-version=2.1

    3.0-preview - https://bitwizards-devops.timehub.7pace.com/api/rest/workLogs/all?$fromCreatedTimestamp=2019-05-17&api-version=3.0-preview

    However, I cannot reproduce the issue I was having and it is certainly possible I am just crazy or was doing something incorrectly yesterday. I think we can close this issue and I will open a new one and provide better detail if it starts happening again.

    Thanks Andarth!

    0
    Comment actions Permalink
  • Avatar
    7pace tech support

    Thanks for the info!

    >The 3.0 does not group from what I can tell, correct

    Yes, you are right, in API v3 all groupings should be done on your side.

    Some insights: a new version of API will have new powerfull features, including grouping.

    Please feel free to contact us at any time!

    Regards,

    Andarth!

    0
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk