Small and medium business | Business Central, N...

in-filter expression not working in odata/api

(1) Share

Report

Posted on by Nick

I'm having issues with the in-filter expression in odata. It is simply not working in both an api endpoint or a odata web service.

Is is documented here:

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/webservices/use-filter-expressions-in-odata-uris

https://learn.microsoft.com/en-us/odata/webapi/in-operator

When I try

query?$filter=resourceNo in ('USERA','USERB')

the filter is not applied at all (no error, simply the results as if no filter is applied at all)

If I use

query?$filter=(resourceNo eq 'USERA' or resourceNo eq 'USERB')

it works as expected.

This is against latest version of cloud sandbox (23.2.14098.14274) and the field is a normal code[20] field, no flowfield or something (although that shouldn't matter).

An I doing something wrong here or is this an issue in BC?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (2)

Answers (0)

Suggested answer

YUN ZHU 99,086 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

Hi, I remember BC does not support in-filter expression. I just tested it again and it does not work. I checked the information on the Internet, and except for Microsoft's documents, no other experts mentioned that in-filter expression can be used.

https://api.businesscentral.dynamics.com/v2.0/c8558e71-6ad8-4fcd-9f29-3ca165b41bbe/Sandbox223/ODataV4/Company('My%20Company')/VendorLedgerEntries$filter=Entry_No in (1760,1762,1768)

Hopefully other experts can give you better advice.

Thanks

ZHU

Was this reply helpful? Yes No
Nick 4 on at

Like (0)

Report
Copy link

Link copied!

The 404 in your test is because you miss the ? before the $filter statement. But thanks for testing.

Was this reply helpful? Yes No