Possible Where Exists() Optimized load BUG

[gaidamichal]

Hello,

I've encountered a strange behavior in Where Exists(). When I use another name for the previously loaded filed I get an unoptimized load but when I rename the other field to match the field name I'm back to optimized. I've attached a sample app for this purpose:

1. Simple Where Exists(Dim1)

Result: Optimized load

2. Changed the filter dim name to Dim5 - Where Exists(Dim5,Dim1)

Result: Unoptimized load

3. Added field Dim1 as Dim5 to the original table, the clause is the same - where Exists(Dim5,Dim1)

Result: Back to optimized load

This feels like a bug in optimized load not being used despite meeting the criteria. Have any of you encountered such behavior? Finding that out saved me a lot of time by simply adding additional field alias.

[jsebrightqi]

This is still an issue on cloud and windows.

[marcus_sommer]

I'm not sure if there is really an issue because it could also mean that Qlik knows that both fields are identically respectively there might be just a single field (one field-id with n field-names).

Creating the fields in different steps and/or ensuring that they are not identically by adding/removing any values or applying a different load-order or similar measures may change the behaviour.