Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
MartW
Partner - Specialist
Partner - Specialist

dummy filter value errors in N-printing

Goodday,

 

In use:

- Qlik Sense: May 2023 version (no Qlik Cloud)

- N-printing: May 2023 version

 

I've got a couple reports that we are restructuring and redefining.

in the old reports we combine 20 or so Qlik apps into 1 report this report is duplicated and also created for the 3 regions.

so within N-printing we got 4 report N-printing can generate. 

- Combined report

- Region A report, Region B report and Region C report

 

In the older reports the Region reports are not always the same. Some mis information from a specific app. in the old reports this was not an issue because the reports were created individually and maintained individually. This was time-consuming.

For the new reports I've created a master N-printing file and report (replacement for the combined report). This report will be duplicated (keep the same filters) for Region A to Region C. The only thing to add in the region specific reports are the region filters.

 

Now the problem I'm facing.

like I said earlier, in the old situation not all sections of the region specific reports where all there. Some mis sections in the report. As an example, the financial section is created in Region A reports while an other region might mis the sales section of the combine report. To fix this I added all regions as dummy values in the 20+ Qlik Sense reports.  but for some reason the a region specific report keeps Erroring and I don't know why. 

After a while I can see that Region A reports keeps erroring. The other Regions work fine and the combined report works also fine.

Things I have tried in the Region A report:

- Removed the Region filter: report runs fine

- changed region filter to an other region: reports runs fine

- checked all Qlik Sense apps if Region field had all 3 regions in them: all apps have Region field in the app with 3 options to select from (Region A, B and C) therefore if region A is selected It should not error.

 

Error Screenshot:

This is the error I'm getting. From what I found online this is a generic error N-printing throws so I cannot pin point where N-printing is encountering an this error.

MartW_1-1693992995202.png

 

NOTE:

Within the Qlik apps if I select and dummy region the objects return this value (see screenshot)

MartW_0-1693992434434.png

 

 

Labels (1)
2 Solutions

Accepted Solutions
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi, 

It is all bit haotic I would say. The error you see is because something is not returning values you expect to get in the scenario. The fact that you get this Qlik Sense error is already red flag (which by the way looks to me like sort of extension object or object which is not supported officially by Qlik as I have never seen one like that before - are you sure your Qlik Sense app meets all requirements?)

I dont know how your report needs to look like and how much they are different between "combined" and "a","b" and "c". I always say that NPrinting development is dependant in 90% on how you do your stuff in Qlik Sense or Qlikview. Design, preparation for such custom thing needs to be done in Qlik Sense and you need to make sure you check for unsupported things or things which logically may not behave properly (like calculated dimensions, set analysis overwriting filter selections, anything different than ordinary).

Your scenario can be built using Pixel Perfect template I am assuming as that is the one which gives you flexibility of hiding and showing parts of report based on content. 

Any form of conditional hide/show directly in Qlik Sense is not really supported - as you cannot use objects in template which sometimes exists and sometimes dont...

Your question is not typical, straight forward one where you can get simple answer. Answer to your question is "it depends" and we would need to have hands on your template, Qlik Sense app, required output, applied filters and only then we will be able to say why something is not working.

cheers

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.

View solution in original post

MartW
Partner - Specialist
Partner - Specialist
Author

Got it fixed. it turns out that  N-printing was not the issue but the Qlik app.

there was a dummy region field in a specific app. therefore N-printing could not make the selections it needed to make for a specific object. it was difficult to find because the correct field was Also called Region in the load script there were 2 fields that where called region : 1 like this [Region] and 1 like this [ Region]

 

View solution in original post

4 Replies
Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

Hi, 

It is all bit haotic I would say. The error you see is because something is not returning values you expect to get in the scenario. The fact that you get this Qlik Sense error is already red flag (which by the way looks to me like sort of extension object or object which is not supported officially by Qlik as I have never seen one like that before - are you sure your Qlik Sense app meets all requirements?)

I dont know how your report needs to look like and how much they are different between "combined" and "a","b" and "c". I always say that NPrinting development is dependant in 90% on how you do your stuff in Qlik Sense or Qlikview. Design, preparation for such custom thing needs to be done in Qlik Sense and you need to make sure you check for unsupported things or things which logically may not behave properly (like calculated dimensions, set analysis overwriting filter selections, anything different than ordinary).

Your scenario can be built using Pixel Perfect template I am assuming as that is the one which gives you flexibility of hiding and showing parts of report based on content. 

Any form of conditional hide/show directly in Qlik Sense is not really supported - as you cannot use objects in template which sometimes exists and sometimes dont...

Your question is not typical, straight forward one where you can get simple answer. Answer to your question is "it depends" and we would need to have hands on your template, Qlik Sense app, required output, applied filters and only then we will be able to say why something is not working.

cheers

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.
Frank_S
Support
Support

@MartW 


If I understand your requirement correctly:

1. you are creating a report from multiple Qlik Documents

2. you are using filters/dimensions across multiple documents.

 

If these assumptions are correct, I would suggest the following.

1. Create a single qlik source document (QVW or QVF) that contains all the data needed for your report.

2. Build your report from this single document and create all filters based on this document.

 

Dimension values from different documents cannot be linked.

ie: 

country > documentA

country> documentb

 

If you create a filter from documentA, it will not filter the results for documentB.

 

So if the assumptions above are correct, using a single QVW or QVF containing all the data should solve this 

"After a while I can see that Region A reports keeps erroring. The other Regions work fine and the combined report works also fine"

 

Kind regards...

Please remember hit the 'Like' button and for helpful answers and resolutions, click on the 'Accept As Solution' button. Cheers!
MartW
Partner - Specialist
Partner - Specialist
Author

Got it fixed. it turns out that  N-printing was not the issue but the Qlik app.

there was a dummy region field in a specific app. therefore N-printing could not make the selections it needed to make for a specific object. it was difficult to find because the correct field was Also called Region in the load script there were 2 fields that where called region : 1 like this [Region] and 1 like this [ Region]

 

Lech_Miszkiewicz
Partner Ambassador/MVP
Partner Ambassador/MVP

oh boy... I have seen those few times - recipe for disaster 😄

 

cheers Lech, When applicable please mark the correct/appropriate replies as "solution" (you can mark up to 3 "solutions". Please LIKE threads if the provided solution is helpful to the problem.