FAQ/filtering-in-dashboards.md
... ...
@@ -2,7 +2,7 @@
2 2
3 3
To apply filters in a dashboard, all reports included in the dashboard must contain the same filter.
4 4
5
-**New default behavior for Izenda dashboard filtering** (10/31/2013 - DLL v6.6.5052) looks at column names **ONLY** for matching report filters for dashboard filtering purposes.
5
+**New default behavior for Izenda dashboard filtering** looks at 'fully qualified' column names for matching report filters for dashboard filtering purposes by default.
6 6
7 7
---------
8 8
... ...
@@ -37,10 +37,19 @@ To apply filters in a dashboard, all reports included in the dashboard must cont
37 37
38 38
--------
39 39
40
-**The default behavior in _classic_ Izenda is to look at _fully qualified_ column names:**
40
+AdHocSettings.UseColumnNameForDashboardCommonFilters = True;
41
+
42
+ - Fully Qualified Name (EXample: View.ColumnName)
43
+
44
+AdHocSettings.UseColumnNameForDashboardCommonFilters = False;
45
+
46
+ - Use 'ColumnName' Only
47
+--------
48
+
49
+**The default behavior in _classic_ (Pre v6.6) Izenda is to look at _fully qualified_ column names. During v6.7 the default was to use ColumnName only. The current default value is AdHocSettings.UseColumnNameForDashboardCommonFilters = True;**
41 50
42 51
_dbo.suppliers.country_ _**IS NOT**_ _dbo.employees.country_ - though they may have many of the same values or the exact same- thus filters do not show up in dashboards at all for the above situation.
43 52
44
-To re-enable classic behavior, fully qualified column names for dashboard filtering, in your deployment after upgrading:
53
+To enable datasource-specific behavior, fully qualified column names for dashboard filtering, in your deployment after upgrading:
45 54
46
-``AdHocSettings.UseColumnNameForDashboardCommonFilters = false;``
... ...
\ No newline at end of file
0
+``AdHocSettings.UseColumnNameForDashboardCommonFilters = true;``
... ...
\ No newline at end of file