Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Andrew_Kruger
Employee
Employee

Filtering an object in a report (Tabular and PixelPerfect Report authoring)

Since releasing our templated reporting capability (Tabular and PixelPerfect) a few report developers have asked about the ability to present comparative analytics in a report where one object is filtered different than a peer object.  Those familiar with Qlik NPrinting reference this capability as Object Level Filters.   

In Qlik Cloud Analytics reporting for Tabular and PixelPerfect authoring this can be achieved by using Alternate States.   Our Qlik Cloud Analytics reporting capability maximizes the power of bookmarks in controlling report filtering which includes definition of Alternate State data reductions.  With objects assigned to different selections states you can achieve comparative report presentation requirements.   

In summary  

  1. if you had a report for which you always want to show an alternate view of an object you would create a filter to be used in the task definition that captures the alternate state value.  
  2. If you had a report for which there is recipient specific object view you would create a filter for each recipient that has the alternate state criteria  per user 

In the attached example Sense App with PixelPerfect report, you will see there are two objects in the app that are associated with different states.  

AltStateYear1.pngAltStateYear2.png

 

You can use the in app filters if you want to run a On-Demand report (sample OD download attached), or you can create a task level filter to manage the different states of the objects used in the report (pictured below).  In this case there is a definition for the month and year of each object – this filter is used at the task level. 

Filter Pane Alt state.png

Be aware, if you are getting into date-based filters (as I did in this example) you do need consider the data types when using auto-calendars (or any other data type for that matter).  In the example app, the standard auto-calendar was used in the load script – the resulting filters are seen above.  See that I used two different strategies for the Year filter in this example - this is a result of the Dual field.    

Our Community Ideation forum is up to date and this recent post PixelPerfect reporting and beyond! shares an update on the current reporting outlook.  The opportunity to drive a deeper integration for reporting use cases within Qlik Cloud Analytics has presented capabilities like filters and alternate states  – give it a shot!   

Labels (4)
1 Reply
F_B
Specialist II
Specialist II

Well, thank you!