Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
I am having an issue with gauge imported from Qlik Sense into Nprinting.
In QS, my gauge looks like that:
I imported it as an image but when I print it out into pdf, it does not seem to be working. The value of the measure is not shown and it looks like that:
Can anyone help me please?
Thank you.
Gerald
Hi Everyone,
we have the same exact issue using master calculations references limitation, this very annoying for customers because they have to change all expressions and break them out in order to work, e.g.
Master Dimension:
([Importe notas]+[Importe facturas]) -(-[Importe devoluciones]) --> This doesn't work until break down to:
((sum(importe_nota))+(sum(importe_factura)) -(-(sum(importe_devolucion)/ -1)))
We opened a support case "00009042: Error Entity Output" and they don't even know why this happens. Hope the employees in this thread make comments to R&D.
NOTE1: This happens with Pivot Table, Gauge chart and Bar/line chart so far.
NOTE2: Using Mail and deploy for reports generation is working fine using master dimensions calculations
keep us posted whats the outcome of your case.
cheers
Unfortunately the case was closed and they just told me the master items are not supported but as somebody commented this seems like a bug.
This is a joke and it makes me angry. Whoever gave you that answer from Qlik support simply made up excuse without backing it up with the facts (unless they provided documentation)?
Lets look at official documentation:
I am using Master Measures and Master Dimensions in all my projects. They work and never were unsupported. Such statement from Qlik is big and I would hold them accountable regarding this statement if that would happened to me - to be honest I am still trying to get official comment but on that later at the bottom of this comment...
I need to explain also that in my master measures I am NOT referencing other master measures which is why I am not experiencing this issue. I never liked that option anyway so it is not a problem for me.
Regarding holding Qlik accountable to their statement I would request clarification. Term "Master Item" is covering too many things. Qlik needs to be clear if :
If any of this is not supported - this needs to be communicated officially, placed in https://help.qlik.com so we can know which versions of NPrinting are affected.
@Ruggero_Piccoli, @Frank_S - can you guys comment on this?
also I had rather heated conversation with @Frank_S under this article: https://community.qlik.com/t5/Testing-Documents/NPrinting-and-Master-Items-Usage-via-Qlik-Sense-Conn... which was then removed from community and I was never able to find it back. There I have raised my concerns regarding "wording" used when describing master items support with NPrinting and demanded that exact clarification and declaration what is supported.
I totally agree because I have to try to explain this behavior to our customers while the documentation is not very clear about this kind of issue/bug/limitation.
Hello,
are there any news meanwhile? We have run to the same problem and it is not purposeful to replace the master kpis in the dashboards now again with the formulas.
Hi @TimB ,
There are not news at the moment. Please open a support ticket with all details we need to reproduce the issue.
Best Regards,
Ruggero
Hi,
i have received a workaround which could fix the issue:
- On the Qlik Sense server, open, as a Windows Administrator, "C:\ProgramData\Qlik\Sense\Engine\Settings.ini".
- Add a new line with "EnableRefMasterMeasure=1".
- Save the file.
- Restart Qlik Sense Engine Service.
- Test again the issue.
Hi @TimB ,
Could you confirm that this workaround works in your case? Thanks a lot.
The complete set of steps is:
I highlighted the ones I added compared to your list.
I sent it privately to some people having the issue and I'm waiting for feedbacks, so they will be appreciated, thanks.
Best Regards,
Ruggero
NOTE: The above setting is available for versions of Qlik Sense from February 2021 GA release.
Hi,
of course i confirm that the workaround works in our applications, otherwise I would not have posted this.
I have already given feedback in the ticket.
Regards