Skip to main content
ManginiL
ManginiL
December 14, 2023
Solved

Entry Date Incorrect - API Insert

Hello - I am using v15 of the API to insert items as issues. I have a subset of items that inserted with an incorrect entry date and need to troubleshoot. Note this is not happening for all items. 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
ManginiL
ManginiLAccepted solution
December 15, 2023

Just to follow up here with the solution - because we were using test data and our logic was using an ID number as a unique identifier to connect to the correct issue. When new items were entered it overwrote the previous test data as an update rather than being inserted as new. That is why the entry date was incorrect. This will not be an issue as we move to production as the ID will always be unique.

View in thread

3 replies

lgaertner
lgaertner
Level 9
December 15, 2023

Hi,

 

I think to help you, we will need some more information concerning your API call.

 

 

Besides that, did you check the Task Constraint of the tasks?

 

Regards

Lars

Translate
ManginiL
ManginiLAuthor
December 15, 2023

Sure - we are testing a version upgrade in our lower environment and had a subset of issues that came over with an entry date that did not match the date of insert.

 

 

In my case the entry date is showing a 1/6/2022.

 

 

In another case the issue had an entry date of March 24th, 2022.

 

 

In both cases, the issue entry date should have been December 13th, 2023 –

Translate
ManginiL
ManginiLAuthorAccepted solution
December 15, 2023

Just to follow up here with the solution - because we were using test data and our logic was using an ID number as a unique identifier to connect to the correct issue. When new items were entered it overwrote the previous test data as an update rather than being inserted as new. That is why the entry date was incorrect. This will not be an issue as we move to production as the ID will always be unique.

Translate
Terms & ConditionsAccessibility statement

Loading footer...