we have noticed that when a link entitiy has its root filter set to the OR type, despite the fetchxml being correct, the generated QueryExpress C# code is not. It does not create a new filterexpression and the default one is of type AND.
This PR fixes the issue by appling the same logic used for OwnersType.Sub also for ownerType == OwnersType.Link (only when filter is of type OR and there is at least one condition).
The following screenshot shows the generated code before and after the fix:
Hi,
we have noticed that when a link entitiy has its root filter set to the OR type, despite the fetchxml being correct, the generated QueryExpress C# code is not. It does not create a new filterexpression and the default one is of type AND.
This PR fixes the issue by appling the same logic used for OwnersType.Sub also for ownerType == OwnersType.Link (only when filter is of type OR and there is at least one condition).
The following screenshot shows the generated code before and after the fix: