Skip to main content
Announcements
Live today at 11 AM ET. Get your questions about Qlik Connect answered, or just listen in. SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
yblake
Partner - Creator II
Partner - Creator II

selectValues extension API do not unselect last selected value

Hi,

I use the following code to select / unselect dimension values from D3 click event :

function clickValue(d,i) { 

  var dim = 0, value = d.dimensionid; 

  self.selectValues( dim, [value], true );

}

The dimensionid is populated from hypercube dimension value qElemNumber.

This was working well until Sense release 2.0.

Since release 2.0, unselecting the last selected value has no effect (it remains selected in the toolbar). However, a second click on the same value makes the unselection working...

So the first question is : Why does the selectValues extension API does'nt work when clicking once the last selected value ?

If I use a simple extension with jquery and "qv-activate" event it does work well. The second question is : How could we handle the "qv-activate" event within D3 ?

Replacing

.on("click", clickValue)

By

.on("qv-activate", clickValue)

doesn't work.

Thanks for any help

12 Replies
Not applicable

Good work reporting the bug. I also stumbled on this when updating my last extension too.

I implemented a swipe selection that might be of interest to you. I use the qv-swipestart, qv-swipeupdate and qv-swipe to get it working.

Check it out here if your interested:

KF-Cards Qlik Sense Extension

yblake
Partner - Creator II
Partner - Creator II
Author

Hi Karl,

Your work is brillant, i would say as ever.

I just read this from Qlik Sense 2.2 beta release notes :

Qlik Sense selectValues extension API does not unselect last selected value

Jira issue ID: QLIK-37933

Description: Unselecting the last selected value would have no effect using the extension API.

We'll give a trial very soon and keep the community informed.

yblake
Partner - Creator II
Partner - Creator II
Author

Hi,

This issue is solved in Sense 2.2 (Tested on QS Desktop 2.2 Beta).