I've tried to reproduce it on latest dashbuilder 6.2.x. It works fine tough. I created two KPIs on the same dashboard and fed them from two different data sources and tables. When I filter by a column that exists in both tables both kpis are filtered correctly. Clicking on chart or in a filter form it makes no difference. I need more info to reproduce it.
For DV 6.1 use, it appears you cannot reproduce the problem. Which is good. The only suggestion I would make would be to test this scenario off your master. Because this is where this issue was seen. And if you do see it, then this BZ can be updated to target upstream.
As mentioned, this is not reproducible neither on master nor 6.2.x. Setting status to MODIFIED.
Just playing with BPM Suite 6.1.0 ER6 and I'm not sure that the current behavior is desired. Please review the steps I used below and let me know what you think: 1) Create 2 data sources that both have identically named property. For simplicity use CSV file data sources based on following 2 files. Notice that both data sources have the "age" property: > cat people.csv id,name,age 1,Jan,30 2,Dan,30 3,Sam,50 > cat cars.csv id,car,age 1,BMW,10 2,Porsche,10 3,Pontiac,30 2) Create 2 Pie chart KPIs on one page, one displaying (X axis: age, Y axis: count of IDs) for people, the other for cars. 3) Create dashboard filter panel to include Car's age property. 4) Filter by clicking charts (click 30 for car's age) or using filter panel (enter from 30 to 30). What I find problematic is that People's ages are filtered too - even though we are filtering on car's age. What do you think of this behavior? Shouldn't filtering be isolated on per-datasource basis?
I would agree, filtering should be based on datasource.column. Right now it appears based on column, regardless of datasource. Which seems you would get unintended filtering.
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.
Closing as NOTABUG, as no changes were made for this BZ.