FetchXML use of unsupported condition should throw error

[HardenTor]

I was wondering why a fetchXML string with
<condition attribute='MyAttribute' operator='begins-with' value='<SomeValue>' />
is ignored in offline mode but evaluated in online mode on D365.

When using the 'like' operator instead of 'begins-with' it works as expected.

It took me some time to find out that the 'begins-with' operator is not supported by JSBridge.

Would it be feasible to raise an error message in case unsupported operators are used in fetchXML strings?

[Maros316]

Hi thanks, it is good point. I will discuss this solution with my colleagues.

[MarekEstokResco]

Thanks for reporting the issue, we appreciate it a lot!

I agree that it is a good idea to not just ignore conditions with unsupported operators. However, it would be a breaking change to existing implementations. It is likely that the problem is deeper than API layer, so we need to investigate a bit more and find a way how to correct this in a robust way.

We will record this defect in our bug-tracking system and investigate how can we improve this. We will let you know here how it proceeds.

Thanks again for reporting this problem.