Tab Container and NPrinting On-Demand reorting

[TimB]

We are currently using Qlik Sense November 2025 Patch 7. The requirement is to export the corresponding NPrinting On-Demand report depending on the current selection.

Since the On-Demand Reporting object from the Qlik Dashboard Bundle only allows a single fixed On-Demand report to be configured, we previously created one button for each NPrinting report and controlled the visibility of the buttons using the old Tab Container.

As the old Tab Container will be removed in a future version, we need to migrate to the new Tab Container or another alternative. However, neither the new Tab Container nor the Layout Container supports the On-Demand object.

Is there any alternative solution for this use case, or is support for the On-Demand object planned for future releases?

[Greg_Taffer]

Here is an Alternative Solution:

Variable-Driven Buttons & Conditional Show

You can bypass container limitations by placing your On-Demand reporting objects directly on the sheet and controlling their visibility with show conditions tied to a variable.

1. Set up the Variable: Create a variable, for example, vReportSelection.
2. Create Navigation/Action Buttons:
   • Add a native Qlik Sense Button to your sheet for each NPrinting report.
   • Under Actions and navigation, add an action to Set variable value.
   • Set the Variable to vReportSelection and the Value to a unique identifier for that report (e.g., ReportA).
3. Configure Conditional Show:
   • Place the On-Demand Reporting objects on the sheet and configure each one to the desired NPrinting report.
   • In the properties of the first On-Demand object, expand Add-ons > Data handling > Show condition.
   • Enter the condition: =vReportSelection = 'ReportA'.
   • Repeat this for the other On-Demand objects, substituting the condition with their respective report identifiers. 

[TimB]

Thank you for the suggestion, but unfortunately this is not feasible for two reasons:

1. The On-Demand object does not provide a show condition. Therefore, the export button previously had to be placed inside the Tab Container in order to hide it.
   
   
   
2. In my case there are 12 different reports. If we used show conditions, the 12 buttons would have to be placed in different locations, which would make the layout very difficult to maintain.

[Lech_Miszkiewicz]

I second @TimB question

I am assuming the OnDemand button has to be rewritten to support new framework and styling (like other objects are slowly getting). With current version indeed it is not possible to hide/show those buttons and obviously it is rather critical gap / functionality which has been taken away. 

@Greg_Taffer - I suggest you check with internal peers on suggestion how we can handle it. I am assuming we need to wait for next release or maybe just check just released 2026 May version. I will be testing it so I will comment in few hours

cheers

[Lech_Miszkiewicz]

Hi @TimB ,

I just did further testing and indeed this is breaking change - still not resolved in May 2026 version. 

@Greg_Taffer - I guess this needs to be reported as support ticket as there is no workaround for it. (don't trust AI agents saying it works as it does not - agents are not testing their answers, we do! 🙂 )

cheers

Lech

[Sunilsahu_345]

I can confirm the behavior described here—this is indeed a limitation with the current On-Demand Reporting object, and it becomes very visible when moving away from the legacy Tab Container.

While there’s no clean 1:1 replacement at the moment, one approach that worked reasonably well for us (though not perfect) was to decouple the user interaction layer from the On-Demand objects entirely.

Instead of trying to dynamically show/hide the On-Demand buttons, we handled report selection via a variable-driven UI (using native buttons or even a filter pane styled as a selector), and then placed all On-Demand objects in a fixed “export zone” of the sheet.

To keep the layout manageable with multiple reports (we had ~10), we grouped the On-Demand objects in a structured grid and used visual cues + disabled-state messaging to guide users. For example:

• Only one “active” report is visually highlighted based on the variable selection
• Other buttons remain visible but are clearly marked as inactive (using text objects layered nearby)
• A small instruction text dynamically reflects the current selection (via =vReportSelection)

This doesn’t truly hide the objects, but it reduces user confusion and avoids layout fragmentation.

Another angle worth considering (depending on your architecture) is whether some reports can be consolidated at the NPrinting level. In a few cases, we replaced multiple report buttons with a single parameter-driven report, where filters/selections control the output. That reduced the number of On-Demand objects significantly.