Bug 1179516 - Clicking on chart item don't filter other KPIs properly
Summary: Clicking on chart item don't filter other KPIs properly
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Dashboard Builder
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: 6.2.0
Assignee: David Le Sage
QA Contact:
David Le Sage
URL:
Whiteboard:
Depends On: 1181181 1225617
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-01-07 00:48 UTC by Walter
Modified: 2015-09-29 00:56 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1181181 (view as bug list)
Environment:
Last Closed: 2015-09-29 00:56:50 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Workspace and Dashboards (77.40 KB, application/zip)
2015-01-07 01:45 UTC, Walter
no flags Details

Description Walter 2015-01-07 00:48:52 UTC
Description of problem:
I have a dashboard with 2 bar charts (NVD3) using distinct datasources (SQL).
Both have a column named "Test". When I select a bar from the first chart, the second chart is updated, but the filter is wrong. 
If I use the filter in the left side, the bug doesn't occurs.

Version-Release number of selected component (if applicable):
6.2 (trunk)

How reproducible:


Steps to Reproduce:
1. Add two bar charts to the dashboard, using distinct data-sources. Both datasources must have columns in common.
2. Click in a bar from the first chart.

Actual results:
Data is shown wrong, messed.

Expected results:
Data is shown correctly

Additional info:
The bug only occurs if I filter from the chart. Using the filter on the left side, bug don't occurs.

Comment 2 Van Halbert 2015-01-07 00:56:29 UTC
Please use the admin user to export the dashboard and workspace.  Should have files with the following extensions:

(workspace) .kpiex
(dashboard) .cex

Comment 3 Walter 2015-01-07 01:45:30 UTC
Created attachment 977041 [details]
Workspace and Dashboards

Workspace and Dashboard files attached

Comment 4 Van Halbert 2015-01-07 03:03:17 UTC
Are these files from DV 6.0 dashboard?

Comment 5 Van Halbert 2015-01-07 03:05:13 UTC
Why I ask are these from DV 6.0, because when I export dashboard and export workspace, I don't get a workspace like this.

Comment 6 Van Halbert 2015-01-09 14:46:15 UTC
Walter,

Can you test with DV 6.1 to see if your issues are resolved?   There have been many improvements in Dashboard Builder.

Thanks.

Van

Comment 8 Walter 2015-01-09 21:10:32 UTC
Van, 

I tested with the master branch of github. It is the 6.1?
I forked the code and fixed it. I don't think mine solution is the best, but worked for me. You could take a look at: https://github.com/walteram/dashboard-builder/commit/fc6d294054486b1c6d638a1a3c18ffe8ac133702

Comment 9 Van Halbert 2015-01-09 21:14:52 UTC
We're using version 6.0.3.

Also, I'll need to post this BZ to the BRMS BAM component so that they can apply the change.

Comment 11 Van Halbert 2015-04-06 13:22:47 UTC
Dashboard builder QE has seen a similar issue.  Not sure if it will get patched on its 6.2 release.

Comment 12 Van Halbert 2015-06-11 16:20:50 UTC
Posted by David on the BPM BZ:

The expected filtering behaviour is the following:

1.- User can define "shared" properties across several data set providers. Basically, a property with the same id. at least in two different data providers.

2.- If we are building a dashboard which refers to two or more data providers containing shared properties and we try to filter by a shared property then any of the KPIs containing such property will be filtered.

3.- Shared properties can be useful for implementing "join" like filter behaviour which allows for filtering several KPIs belonging to different data providers to filter at the same time.

4.- We can disable the join like behaviour above just by adjusting the property ids on the data provider column definition screen. We must ensure the property ids are unique and do not clash between data provider definitions. 

The example described by @Jan is working as expected. However, if we do not want the People KPI to be filtered then we can proceed as #4, change the Car's age property to f.i: "carAge". Doing so we differentiate between the Car's age and the People's age.


The current implementation it covers a wide range of scenarios. Changing the underlying implementation can be problematic and hard to implement. We do not recommend it.


One additional thing we can do is to add a section to the user documentation to clarify how this feature works, similar to the above explanation.

Comment 13 David Le Sage 2015-09-03 02:54:28 UTC
Thanks. I have added a new topic ("Dashboard Builder Filters") to the Admin Guide, containing the information outline above.


Note You need to log in before you can comment on or make changes to this bug.