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?
Please sign in to leave a comment.