Filter By type 'Date' to query content

Support
1

I have queried the content by using filter, but have errors in page and also respones error in postman using api. Such as pics below.

ODATA%20error
ODATA error.png953×540 13.7 KB

In postman, the api response is:
{
“message”: “OData operation is not supported.”,
“details”: [],
“statusCode”: 400
}

And this is the data structure of the content
“data”: {
“ID”: {
“iv”: “1234567”
},
“Memory”: {
“iv”: “2019-05-13T10:13:35Z”
}
},

So i want to know what caused this. OData operations is what.

2

Can you show or better post your full query?

3

Thanks for quick reply.
My full query is
https://uatorchsupport.lenovo.com/api/content/manage-roles/testproperty?$filter=data/Memory/iv eq 2019-05-13T10:13:35Z

4

Sorry the above query is in postman,

And in squidex Contents page, the query is $filter=data/Memory/iv eq 2019-05-13T10:13:35Z

5

Looks okay, I will have a look in a few hours.

6

It works for me, I am a little bit confused

7

Oh, I am confused too.:scream:

So, have you ever occured the such error?----“OData operation is not supported.”

I think my query code is OK.

8

Yes, your query code is okay. Which version are you running?

9

I can’t reproduce this issue. it should be already fixed.

:hugs:
by the way, do you know how to build a query for filtering geolocation fields.

10

Thanks for your reproduction. Filtering by geolocations is not supported, because it would require special indices to have near-by searches.

11

I create a new schema and add a content contains type ‘DATE’

And the query works now. Thanks.
(By the way, I don’t know why…)

12

I have the same problem.

I recognize that if I set the datetime field to be ‘Required’ will cause the issue.
Otherwise, an optional datetime field will be working fine.

@Sebastian - hope it’s reproducible for your-side and we can get a fix soon :slight_smile: .

(@woshiaa fyi).

13

Again. Which version?