Unanswered

ICM Connector. What is the correct syntax for time based searches like "CreatedDate gt '2020-05-01T00:00:00'

(0) Share

Report

Posted on by MsFlower Microsoft Employee

When I try that I get an error that CreatedDate should not be a string

I have also tried prepending datetime and get this:

Invalid options specified in OData query. Unrecognized 'Edm.String' literal 'datetime'2020-06-24T19:46:31'' at '43' in 'CreatedDate gt datetime'2020-06-24T19:46:31' and (State eq 'Active' or State eq 'Mitigated') and Type eq 'CustomerReported' and ParentId eq null'

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

v-bacao-msft on at

Like (0)

Report

Hi @MsFlower ,

I did a test on my side, it seems that in the Filter Query cannot use the Date type field as a filter.

Please consider adding Filter Query below this action to use Date as a filter to filter incidents again.

Best Regards,

Was this reply helpful? Yes No
davidBlount Microsoft Employee on at

Like (0)

Report

Is this still the situation? That OData cannot pass a datetime to a query?
This is really clunky.
I need my query to have a datetime filter, otherwise I cant get it to return as the data set being queried is far too large and it times out or is throttled.
So I cannot use the suggested solution above. As it would fail to get me any result set to subsequently filter on
This HAS to be a common use case that this lack of functionality is breaking?
FWIW, here's my error:-
"message": "Invalid options specified in OData query. Unrecognized 'Edm.String' literal 'datetime'2023-10-30T10:23:56'' at '15' in 'CreatedDate gt datetime'2023-10-30T10:23:56' and OwningTenantName eq 'redacted' and State eq 'ACTIVE' and Title eq 'Redacted''."
The formatting of the datetime is exactly matching what is in the ICM documentation, so that is not the problem.
https://icmdocs.azurewebsites.net/developers/IncidentSearch.html#sample-queries

Was this reply helpful? Yes No