Hi Andre,
I will explain more:
The first option:
I create a single entity with TableLines inner joined with TableHeader.
Then i create a computed column in the entity that satisfies this:
((Field1= Enum1::ValueX) || ((Field1= Enum1::ValueY) && (Field2= Enum2::ValueA)))
Now i can't filter this computed column on the entity. So i create an export data project and I filter on this computed column there.
Then 2nd option
I create a view with TableLines inner joined with TableHeader.
Then i create a computed column in the view that satisfies this:
((Field1= Enum1::ValueX) || ((Field1= Enum1::ValueY) && (Field2= Enum2::ValueA)))
Now I create a single entity with this view.
and Now i can filter on the computed column on the entity itself without the need to filter on the data project
I know that the first option, will return everything, then in the data project the filter will happen
in the 2nd option, the filter will be on the entity itself
So does that affect performance if we filter on the entity directly or on the data project?
And how can I test the performance for both options?