SAP Odata filter query returning internal server error

(1) Share

Report

Posted on by darren1372

Hi,

I am using the SAP Odata connector to retrieve table properties from Success Factors.
Using Postman and help from our SAP developer guys I have managed to compile my query (with expand) and get all desired properties.
So far so good.

However, adding a filter seems to break the query, returning an internal server error.
The SAP team have confirmed the date time format and in Postman the following is working:

lastModifiedDateTime gt datetimeoffset '2025-01-05T15:16:23'

However, Power Automate is returning an internal sever error. What is even more frustrating the SAP back end is showing no error.

Here is my workflow / query.

So for I have tried:

lastModifiedDateTime gt datetimeoffset '2025-01-05T15:16:23'
lastModifiedDateTime gt datetimeoffset '2025-01-05T15:16:23z'
lastModifiedDateTime gt datetimeoffset 2025-01-05T15:16:23
lastModifiedDateTime gt datetimeoffset 2025-01-05T15:16:23z
lastModifiedDateTime gt '2025-01-05T15:16:23'
lastModifiedDateTime gt '2025-01-05T15:16:23z'
lastModifiedDateTime gt 2025-01-05T15:16:23
lastModifiedDateTime gt 2025-01-05T15:16:23z

None of the above works.

Any pointers / suggestions would be highly appreciated.
Not a lot of documentation on how to use this connector online, only how to set it up.

Categories:

Translation quality feedback

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

w.p 8,339 Super User 2025 Season 2 on at

Like (0)

Report

@darren1372

try to create a compose action for the date/time offset

$filter: lastModifiedDateTime gt outputs('Compose')

Was this reply helpful? Yes No
stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report

@darren1372 Hi,

Please try $filter=lastModifiedDateTime eq '2025*' , if not

use Initialize variable, then pass it to the fitler.

Was this reply helpful? Yes No
darren1372 47 on at

Like (0)

Report

Hi,

so I have tried:

then:

Still returned internal server error.

Also tried:

This returned:

Any other suggestions @stampcoin @w.p

Was this reply helpful? Yes No
stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report

@darren1372 Hi,

I am wondering if you use other field for the filter, will that work ? ( for example use twoCharCountryCode)

Does it support z or Z ?

if you initialize all string , will that work ?

Was this reply helpful? Yes No
w.p 8,339 Super User 2025 Season 2 on at

Like (0)

Report

@darren1372

i don't know how you calculate the date/time offset, but the Compose output should be 2025-01-05T15:16:23

Or try $filter: lastModifiedDateTime gt '2025-01-05T15:16:23'

Was this reply helpful? Yes No
w.p 8,339 Super User 2025 Season 2 on at

Like (0)

Report

Was this reply helpful? Yes No
darren1372 47 on at

Like (0)

Report

I have tried this morning:

also:

Unfortunately both do not work

I did do a separate query to see what the value of lastModifiedDateTime is via power automate and it's coming out as:

so I tried:

lastModifiedDateTime gt '2025-01-05T15:16:23+00:00'
lastModifiedDateTime gt datetimeoffset '2025-01-05T15:16:23+00:00' - gap between datetimeoffset and date string
lastModifiedDateTime gt datetimeoffset'2025-01-05T15:16:23+00:00' - no gap between datetimeoffset and date string

Again, the above didn't work.

@w.p @stampcoin

Was this reply helpful? Yes No
stampcoin 5,058 Super User 2025 Season 2 on at

Like (0)

Report

@darren1372 Hi,

Thanks for sharing the update.

Have you tried generic GET http ( use power auotmate) against one entity which has lastModifiedDateTime ?

For example, Use send http request.

Get https://...../Customers?$filter=lastModifiedDateTime gt ''

If that works, then use Sap connector for querying one entity.

Another try is ,in the current one flow, use another field for the filter, reduce selection, reduce expand.

Was this reply helpful? Yes No
w.p 8,339 Super User 2025 Season 2 on at

Like (0)

Report

@darren1372

Could you try with the top 5 records to check if the connection works correctly?

If it does, you might also try using a different date column, such as created at.

Was this reply helpful? Yes No