Overview

With the current model-driven app view filters, you can't add related table conditions under OR conditions. 

So, if you want to implement flexible search conditions that combine multiple related tables, the standard UI alone won't meet the requirements, and you'll need to handle it by directly editing FetchXML or something similar. 

However, even if you achieve it by editing FetchXML, for configurations that can't be created with standard features, the behavior isn't guaranteed, and there have actually been cases where the filter results ended up different from what was expected.

Request

On the view filter edit screen, I'd like to be able to:

- Add conditions for related tables under OR conditions  

- Build complex related table conditions using the standard UI  

- Use the equivalent functionality without having to directly edit FetchXML

Potential Benefits

1. The range of requirements that can be met with standard features has expanded

Right now, there are cases where you can't do it with just the standard UI when you want to set up complex conditions that include related tables.  

Being able to set up OR conditions that include related tables with the standard features would let you handle more business requirements within the standard functionality.

2. Reducing reliance on direct FetchXML editing

There are cases where FetchXML editing is used to configure conditions that can’t be achieved with standard features.

If you can set equivalent conditions directly in the view designer, it reduces dependence on advanced customization and allows for easier-to-manage configurations.

3. Improved Flexibility and Maintainability of View Design

By increasing the freedom to set conditions using related tables, it becomes possible to reduce the need to create multiple views or implement workarounds.

As a result, this is expected to improve the flexibility of view design and reduce future maintenance burdens.