AnsweredAssumed Answered

Is time considered when filtering by date using Sugar API?

Question asked by Yury Voloshin on Oct 22, 2018
Latest reply on Oct 25, 2018 by Yury Voloshin

Like • Show 0 Likes0
Comment • 5

I'm trying to filter records by date using an API call like this:

"/rest/v11/RevenueLineItems?filter[0][date_modified][$gte]=" + date

The date variable is originally a timestamp, but so far I've had to separate out the time part and only use the date because the filter would not consider the time when making comparisons. Can anyone tell me if the most recent versions of the API (11.1 and 11.2) can filter by timestamp (taking hours and minutes into account), instead of just by date? Where can I find this information?

Thanks,

Yury

Patrick McQueen

Oct 24, 2018 2:54 PM

Correct Answer

Hi Yury Voloshin,

That GET URL works fine for me when using a valid Oath-Token for the exact same instance you are trying to reach.

Note that I have an additional header setting the Content-Type to application/json.

What platform is defined in your POST to get the access_token? I used "mobile" in this example.

See the reply in context

No one else had this question

Outcomes

Patrick McQueen

Oct 22, 2018 12:38 PM

Hi Yury Voloshin,

Using the date and time formatted as below in the URL worked for me.

In a stock 8.2.0 Enterprise instance with demo data, I received expected results from the following using Postman to test:

GET: https://instance_url/rest/v11/RevenueLineItems?filter[0][date_modified][$gte]=2018-10-14T05:13:51-08:00

I hope this helps.

1 person found this helpful

Actions

Yury Voloshin @ Patrick McQueen on Oct 24, 2018 2:12 PM

Thanks Patrick McQueen! This is really helpful. I've been trying to use Postman to test this endpoint, but I keep running into problems.

I get a new oauth token from this URL: https://<domain>/rest/v11/oauth2/token?grant_type=password&username=<username>&password=<password>&platform=base&client_id=sugar&client_secret

But, when I try to use this token to send to get filtered records using a GET request as shown in the attached screenshot, I get an "invalid access token" error. Do you see any problems with what I'm doing that might explain the error?

Actions

Yury Voloshin @ Yury Voloshin on Oct 24, 2018 2:24 PM

A bigger version of the screenshot

Actions

Patrick McQueen

@ Yury Voloshin on Oct 24, 2018 2:54 PM

Hi Yury Voloshin,

That GET URL works fine for me when using a valid Oath-Token for the exact same instance you are trying to reach.

Note that I have an additional header setting the Content-Type to application/json.

What platform is defined in your POST to get the access_token? I used "mobile" in this example.

1 person found this helpful

Actions

Yury Voloshin @ Patrick McQueen on Oct 25, 2018 6:26 AM

Thanks a lot Patrick McQueen! Looks like the problem was that I didn't have content-type in the request. The request worked when I added it.

Actions

5 Replies

Patrick McQueen Oct 22, 2018 12:38 PM
Mark Correct
Correct Answer
Hi Yury Voloshin,

Using the date and time formatted as below in the URL worked for me.

In a stock 8.2.0 Enterprise instance with demo data, I received expected results from the following using Postman to test:
GET: https://instance_url/rest/v11/RevenueLineItems?filter[0][date_modified][$gte]=2018-10-14T05:13:51-08:00

I hope this helps.
1 person found this helpful
Like • Show 1 Like1
Actions
- Yury Voloshin @ Patrick McQueen on Oct 24, 2018 2:12 PM
  Mark Correct
  Correct Answer
  Thanks Patrick McQueen! This is really helpful. I've been trying to use Postman to test this endpoint, but I keep running into problems.
  I get a new oauth token from this URL: https://<domain>/rest/v11/oauth2/token?grant_type=password&username=<username>&password=<password>&platform=base&client_id=sugar&client_secret
  But, when I try to use this token to send to get filtered records using a GET request as shown in the attached screenshot, I get an "invalid access token" error. Do you see any problems with what I'm doing that might explain the error?
  Like • Show 0 Likes0
  Actions
  - Yury Voloshin @ Yury Voloshin on Oct 24, 2018 2:24 PM
    Mark Correct
    Correct Answer
    A bigger version of the screenshot
    Like • Show 0 Likes0
    Actions
  - Patrick McQueen @ Yury Voloshin on Oct 24, 2018 2:54 PM
    Unmark Correct
    Correct Answer
    Hi Yury Voloshin,
    
    That GET URL works fine for me when using a valid Oath-Token for the exact same instance you are trying to reach.
    Note that I have an additional header setting the Content-Type to application/json.
    What platform is defined in your POST to get the access_token? I used "mobile" in this example.
    
    1 person found this helpful
    Like • Show 0 Likes0
    Actions
    - Yury Voloshin @ Patrick McQueen on Oct 25, 2018 6:26 AM
      Mark Correct
      Correct Answer
      Thanks a lot Patrick McQueen! Looks like the problem was that I didn't have content-type in the request. The request worked when I added it.
      Like • Show 0 Likes0
      Actions

Is time considered when filtering by date using Sugar API?

Outcomes

Related Content

Recommended Content