Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid Date-Time field(s) error if lastUpdatedAfter in getOrders is in iso8601 format (Japan time) #330

Closed
asagawa0519 opened this issue Aug 18, 2023 · 4 comments

Comments

@asagawa0519
Copy link

https://sellingpartnerapi-fe.amazon.com/orders/v0/orders?LastUpdatedAfter=2023-08-18T00:00:00+09:00&OrderStatuses=Unshipped,PartiallyShipped&MarketplaceIds=1VC38T7YXB528&FulfillmentChannels=MFNwould result in the following error.

> JSON.parse(response.body)
=> errors"=>[{"code"=>"InvalidInput", "message"=>"This is invalid input", "details"=>"Invalid date/time field [lastUpdatedAfter]"}]}]

+09:00 is removed and the response is returned normally. Why is this?

If it succeeds

https://sellingpartnerapi-fe.amazon.com/orders/v0/orders?LastUpdatedAfter=2023-08-18T00:00:00&OrderStatuses=Unshipped,. PartiallyShipped&MarketplaceIds=A1VC38T7YXB528&FulfillmentChannels=MFN

@asagawa0519
Copy link
Author

It appears that LastUpdatedAfter must be UTC time.
Therefore, the JTC notation seems to have resulted in an error.
I would like the documentation to clearly state that the time is in UTC.

@Aayush-Kapur
Copy link

Aayush-Kapur commented Sep 21, 2023

Hey @asagawa0519 , shouldn't this be the case(specifying time to be in UTC) for LastUpdatedBefore, ChangedAfter, ChangedBefore or all the other date-time format params?

Also I have created a pull request #335 for only LastUpdatedAfter. Please review.
And if changes have to be made in documentation/description of other date-time params , please let me know.

Copy link

github-actions bot commented May 9, 2024

This is a very old issue that is probably not getting as much attention as it deserves. We encourage you to check if this is still an issue after the latest release and if you find that this is still a problem, please feel free to open a new issue and make a reference to this one.

Copy link

closed for inactivity

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants