Share
ReportHi All,
Is there a limitation with the OData implementation in Finance and Operations?
When I am running the below ODATA api request I am getting undesired results with the wildcard in the ActivityNumber condition and the condition is being ignored. It works fine if I do not include the activity number condition. Please note I had extended the Activities entity to include a projid, this all works perfectly.
This returns results where ActivityNumber contains 'AN101' which is not expected as the clause is ne with a wildcard.
....operations.dynamics.com/data/Activities?$format=json&$filter=ProjId eq '1011*' and ActivityNumber ne 'AN101*'&cross-company=true
It DOES work if I do not use a wildcard in the ActivityNumber comparisons, such as /ActivityNumber ne 'AN1010001'/
....operations.dynamics.com/data/Activities?$format=json&$filter=ProjId eq '1011*' and ActivityNumber ne 'AN1010001'&cross-company=true
It DOES work if I only include the ActivityNumber comparison with a wildcard such :
....operations.dynamics.com/data/Activities?$format=json&$filter=ActivityNumber ne 'AN101*'&cross-company=true
All responses (
Answers (
426
