NPrinting Pixel Perfect Report Date Filter Condition

[rtaraka]

Hello,

Currently I'm looking for a help with passing a Greater than or equals (>=) on date field1 and less than or equal to(<=) on date field 2 with passing one date from filter in  Qlik Sense N Printing Pixel Perfect Layout report with multiple level. 

I'm applying below conditions in the table view in QS and remove Null check box.

Datefeild1(BILL_RULE_STARTS): =aggr(Only({$ < BILL_RULE_STARTS={"<=$(=max(BEGIN_DATE))"}> }BILL_RULE_STARTS),BILL_RULE_STARTS)

Datefeild2(BR_END): =aggr(Only({$ < BR_END={"<=$(=max(BEGIN_DATE))"}> }BR_END),BR_END)

Begin date field is date dim with all the date (history and Future).

WIth above condition able to make the QS report work as expected with data filter part.

Currently I'm using same app to generate the layout to print the data in PDF with multiple level based report. Using On Demand functionality using Button option providing a QS NPrinting Pixel perfect as a Button. So use can filter the data as needed, verify it with QS table in a tabular format then hit the output button to printing the PDF version of the report.

Initial observation is When we apply any condition Qlik sense Report  then by default it's starts with equals to sign(=).  If I use any condition like below. 

This <no Title> view  will not be an options to use it.  This future will helps you to see data based on level based hierarchy.

If I don't use any = Operation in any field or any condition then No title view will be enable. So i can use it.

Here is the layout design.

Looking for  help with passing a Greater than or equals (>=) on date field1 and less than or equal to(<=) on date field 2 with passing one date from filter  So I can pass the filter data in the N Printing using No title under levels.

Please let me know if needed more information to get the solution.

[Ruggero_Piccoli]

Hi,

I'm sorry but I'm not sure I understood your goal. What you want to do is to filter the whole report by greater and less than two date fields via On-Demand. Correct?

Best Regards,

Ruggero

[rtaraka]

Yes. I'm looking for solution where I can pass a date from Qlik Sense Report. Based on the selected date Report need to filter values by  greater and less than two date fields via On-Demand.

[Lech_Miszkiewicz]

no worries there:

just use set analysis on expression and do not use calculated dimensions as I guess this is the problem you are trying to describe.

cheers

[rtaraka]

I was able to figured out the solution. 

I had two solutions now.

1. Always use the expression is measure instead of a dimension. This will get the No title view under levels. Then apply filter condition on that level node. Under properties - Data -> Filter String. Don't apply any conditions on your QS report filters or don't apply any field setting as always select only one value.

2. Convert all three dates to a number from from the load script. Then Apply Conditions in the template level  hen apply filter condition on that particular level node. Under properties - Data -> Filter String. Don't apply any conditions on your QS report filters or don't apply any field setting as always select only one value. it resolve the solution.

[rtaraka]

Thanks for your input.

[rtaraka]

Thanks Ruggero for showing interest in helping to resolve my issue and trying to understand what questions i have. 

[Lech_Miszkiewicz · Accepted solution]

Great that you have managed to find a solution.

your option no 1 is described in help document and is rather general practice: https://help.qlik.com/en-US/nprinting/May2021/Content/NPrinting/ReportsDevelopment/Qlik-objects-supp...

It is also a lot more efficient from Qlik Sense performance to use set analysis on measures rather than calculated dimensions. 

It is also written which objects are not supported:

It seems you are new to NPrinting - so despite the fact that you managed to find a solution I would encourage you to study help document to learn little bit more about supported configurations! Believe me - it will only benefit you in the future.

Your second solution kind of reminds me about the fact that dates are usually stored as numbers anyway in Qlik so understanding of data type is critical when applying any kind of filter which I have described over here: https://nprintingadventures.com/2019/02/15/the-pitfalls-of-nprinting-filters-part-1-dates-and-duals/ and I keep on touching on this subject each time I speak about filters: https://nprintingadventures.com/category/nprinting/filters/