search

stefanwalther / sense-navigation

Sheet Navigation + Actions for Qlik Sense.
MIT License
88 stars 61 forks source link

sense sheet navigation is not working #64

Closed samybics closed 7 years ago

samybics commented 7 years ago

sheet navigation is not working in single configurator with or without iframe on qlik sense 2.4 server as well as qlik sense 3.0 desktop. Please provide me any sample which works on single configurator

stefanwalther commented 7 years ago

Haven't really tested it in the single configurator, since the main use-case is to use it within Qlik Sense ... What exactly is not working? Which version of sense-navigation (have a look into the .qext file) are you using?

samybics commented 7 years ago

Hi Stefan,

         Sense navigation is not working. When I have four navigation

button with four sheets mapped, The navigation button is not working on the iframe url, where as it works on sense app in hub.

.qext version is :0.8.1 with qliksense 3.0

Thank you

With regards

Arockiasamy Ph : +91 7639018872

On Sat, Oct 15, 2016 at 6:32 PM, Stefan Walther notifications@github.com wrote:

Haven't really tested it in the single configurator, since the main use-case is to use it within Qlik Sense ... What exactly is not working? Which version of sense-navigation (have a look into the .qext file) are you using?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/stefanwalther/sense-navigation/issues/64#issuecomment-253983012, or mute the thread https://github.com/notifications/unsubscribe-auth/AG7OIduIsWpi0AmKt1paa6Lm_33oCjb8ks5q0M7vgaJpZM4KXoJ2 .

stefanwalther commented 7 years ago

HI @samybics ,

sense-navigation was really developed to help with actions & navigations withing Qlik Sense. The next generation of sense-navigation ( #58 ) even extends that. So any scenario you are describing (e.g. jumping to another sheet in a Mashup scenario or in an Iframe just cannot work).

This is not your fault, I should think of how actually an extension like this one should be disabled to be used in single-configurator or in mashups.

So I won't fix, hope you understand, but think about a long term solution, so that this misunderstanding cannot happen again.

Regards Stefan