Incorrect Result for getHyperCubeData when using Master Measures in Viz Expressions about enigma.js HOT 8 CLOSED

Hi @tomomni,
We unfortunately couldn't reproduce this issue, but one of my colleagues suggested that this can be a permission issue: that maybe the authenticated user in node.js/enigma is not the same as the one authenticated via browser (dev-hub)

from enigma.js.

Hi @aihazm,

Thanks for checking this out, it's a really peculiar issue since there is no problem when using linked master measures it only occurs when referencing master measures in a measure expression.

When connecting to an enterprise environment, I am basically running my app as an SSE - on the server using the site certificates for authentication, my user in this case is typically the env service account.

I could see the potential for a permission mismatch issue here however, it's odd that a permissions issue would allow me to get data from adjacent columns in the same visualization (table). Furthermore, I can also recreate the issue when running locally using Sense Desktop too both when I have provided my user/directory info and when I leave it null.

I will take a closer look here, toy around with my user/directory settings and update this post with my findings.

Additionally, would it help if I share a repo with a re-creatable Sense Desktop example (including the QVF)? I can whip something up relatively quickly if you guys will check it out.

Thanks again for looking into this.

-Tom

Mar 10 11:15 EST UPDATE:

Confirmed not a permissions issue. Went to start creating an example app and discovered new information though! In order to trigger the issue, the master measure must have a calculated label expression (ie: 'Sample Measure') and the measure expression referencing the master measure must use a different label (ie: 'Referenced Measure'). Need to do some more testing and will update again with further findings.

Mar 10 14:10 EST UPDATE:

Created a repo with a barebones example: https://github.com/tomomni/engima.js_Issue944_Example

Please let me know if there are still any issues recreating - determined the issue only occurs when the master measure has it's own label expression & the expression referencing the master measure has it's own label (like in the example app). Removing the label expression from the master measure will resolve the issue.

from enigma.js.

Hi @tomomni ,
My apologies for the late follow-up. Thank you for the provided example of reproducing the issue. I am now looking into the issue, and think I have found the cause of the problem that you are experiencing.

Just for confirmation, with your example app & script provided you are getting the following result for getHyperCubeData?

And expected behaviour would be :

from enigma.js.

Hi @wennmo, no worries on the delay - I appreciate you looking into this.

You are exactly correct with the experienced and expected behaviors.

from enigma.js.

Hi @tomomni, thanks for the confirmation. This problem has already been fixed in Qlik Sense SaaS, which is why @aihazm was unable to reproduce it.

Since you are testing against Qlik Sense Enterprise/Desktop Feb 2021, I will look into when/if the solution was introduced for those products.

from enigma.js.

@wennmo, interesting that it's solved in SaaS.

I thought @aihazm might not have been able to recreate the issue because I missed exactly what the trigger was initially - it was only in assembling my example that I realized the issue can only be triggered when the master measure has it's own label expression and the column where the master measure is being referenced has it's own label (like in the example app).

I just tested using enterprise Feb 2022 Patch 2 and the issue still exists as of that version.

from enigma.js.

@tomomni, sorry for the delay but now I finally got a response on when the fix was introduced.

Since Qlik Sense Enterprise for Windows has a different release cadence compared to Qlik Sense SaaS, it has so far not been part of any release for that product. It is however targeted for the May release (but was not part of the February release).

from enigma.js.

I will close this issue for now, since this is not enigma.js related.

There is a fix being planned for the next release of Qlik Sense Enterprise for Windows, and that should resolve the issue.

from enigma.js.