Time zone mismatch

SUGGESTED

Hello Team,

I have a question about the time zone mismatch.

I found the following issue.

To receive customers we use two endpoints:

https://api.columbus.sage.com/uk/sage200extra/accounts/v1/customers
https://api.columbus.sage.com/uk/sage200extra/accounts/v1/customer_views

Using these endpoints I receive the Customer --->> "name": "Customer1"

Endpoint:
https://api.columbus.sage.com/uk/sage200extra/accounts/v1/customer_views
for customer Customer1 ->> "date_time_updated": "2022-05-04T10:05:50.44Z"

Endpoint:
https://api.columbus.sage.com/uk/sage200extra/accounts/v1/customers
for customer Customer1 ->> "date_time_updated": "2022-05-04T10:05:50.44Z"

But, if I use the following request:
api.columbus.sage.com/.../customer_views ge 2022-05-04T10:05:50.44Z and date_time_updated le 2022-05-04T10:05:50.44Z

I cannot find customer Customer1. I think it is a problem with the time zone. Which time zone I should use?

Because this request returns the customer Customer1 - api.columbus.sage.com/.../customers ge 2022-05-04T10:05:50.44Z and date_time_updated le 2022-05-04T10:05:50.44Z

Parents
  • 0

    Just a thought - does it work if you use a larger time interval for the criteria, say a minute each side?

    ge 2022-05-04T10:05:49.44Z and date_time_updated le 2022-05-04T10:05:51.44Z

    After all, saying "ge (time) and le (time)" is actually "eq (time)"

    And the SQL datetime hold milliseconds, but you're only suppling hundredths of a second. So if the value is actually 2022-05-04T10:05:50.445Z, your query won't find it.

Reply
  • 0

    Just a thought - does it work if you use a larger time interval for the criteria, say a minute each side?

    ge 2022-05-04T10:05:49.44Z and date_time_updated le 2022-05-04T10:05:51.44Z

    After all, saying "ge (time) and le (time)" is actually "eq (time)"

    And the SQL datetime hold milliseconds, but you're only suppling hundredths of a second. So if the value is actually 2022-05-04T10:05:50.445Z, your query won't find it.

Children