Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi
We are having an issue whereby the Qlik-button-for-navigation extension that comes as part of the Dashboard bundle shows up in the C:\Program Files\Qlik\Sense\ExtensionBundles\Dashboard-bundle\bundle folder and in the QMC but it is not available in the Hub:
Does anyone know to to rectify this issue?
We are using the February 2021 software with patch 4 installed and running 2 servers, one as a central node and one as a rim node. The extension doesn't appear in either of the hubs as an option but if added to apps previously it still shows and works on the central node but shows as an Invalid Visualization on the rim node.
Thanks
Hey there @Colleen ,
on which QS release are you working?
That extension is deprecated since QS April 2020, in favor of the default object 'Button'.
If you're on QS April 2020 (or later releases) you should be able to see it in QMC mainly for retrocompatibility purposes: in your applications you'll still be able to see the current button for navigation objects, but won't be able to create new ones (this way you can take your time to migrate your objects, without issues for the end users).
You can find more here: Qlik Sense April 2020 - Dashboard bundle - Deprecated Controls
I hope this helps,
Riccardo
Hey there @Colleen ,
on which QS release are you working?
That extension is deprecated since QS April 2020, in favor of the default object 'Button'.
If you're on QS April 2020 (or later releases) you should be able to see it in QMC mainly for retrocompatibility purposes: in your applications you'll still be able to see the current button for navigation objects, but won't be able to create new ones (this way you can take your time to migrate your objects, without issues for the end users).
You can find more here: Qlik Sense April 2020 - Dashboard bundle - Deprecated Controls
I hope this helps,
Riccardo
Okay thanks.
We were on April 2020 but upgraded when we changed servers about a month ago so that is probably what the issue is.
Unfortunately we will have to go through and change all our buttons as it is working on our central node but not on the rim node which is where our users are working.
Thanks for the response.
You should still be able to see the button for navigation extension on RIM nodes, as far as I know
Anyway, if it could be of any help, you could take a look at the Extension Usage Dashboard: AdminPlayBook - Extension Usage Dashboard
It will give you an idea of where your button for navigation extension (and also all the other extension in your environment) have been used
Riccardo