FAQ/filtering-in-dashboards.md
... ...
@@ -1,55 +1,66 @@
1 1
#How Does Filtering In Dashboards Work?
2 2
3
-To apply filters in a dashboard, all reports included in the dashboard must contain the same filter.
4
-
5
-**New default behavior for Izenda dashboard filtering** looks at 'fully qualified' column names for matching report filters for dashboard filtering purposes by default.
3
+[[_TOC_]]
6 4
7
----------
8
-
9
-- **_I create Report A:_**
5
+##About
6
+To apply filters in a dashboard, all reports included in the dashboard must contain the same filter.
10 7
11
- _Employee Table:_
8
+**The new default behavior for Izenda dashboard filtering** looks at 'fully qualified' column names for matching report filters for dashboard filtering purposes by default.
12 9
13
- Last Name
10
+##Example
11
+Using the Northwinds database
14 12
15
- Country
13
+1) Create Report A using the Employee table:
16 14
17
- **Filter 1** : Country
15
+ * Fields:
16
+ * Last Name
17
+ * Country
18 18
19
- **Filter 2** : Last Name
19
+ * Filter 1: Country
20
+ * Filter 2: Last Name
20 21
22
+2) Create Report B using the Supplier table
21 23
22
-- **_I create Report B:_**
24
+ * Fields:
25
+ * Supplier Name
26
+ * Country
23 27
24
- _Supplier Table:_
28
+ * Filter 1: Country
29
+ * Filter 2: Supplier Name
25 30
26
- Supplier Name
31
+3) Create a dashboard from these two reports
27 32
28
- Country
33
+ * Expected dashboard filter: Country
29 34
30
- **Filter 1** : Country
35
+##Explanation
31 36
32
- **Filter 2** : Supplier Name
37
+**The default behavior in _classic_ (Pre v6.6) Izenda is to look at _fully qualified_ column names.**
33 38
34
-- **I create a dashboard from these two reports:**
39
+**During v6.7 the default was to use ColumnName only.**
35 40
36
- _Dashboard contains Filter_ : Country
41
+**The current default value is to use the fully qualified field name (AdHocSettings.UseColumnNameForDashboardCommonFilters = True;)**
37 42
38
---------
43
+Although they may share similar values or have the exact same values, _dbo.suppliers.country_ _**IS NOT**_ _dbo.employees.country_ . Because of this, the filter in the example will not show up in the dashboard in vanilla Izenda.
39 44
40
-AdHocSettings.UseColumnNameForDashboardCommonFilters = True;
45
+To disable datasource-specific behavior (fully qualified column names) for dashboard filtering, you will need to change the UseColumnNameForDashboardCommonFilters to false in your deployment after upgrading.
41 46
42
- - Fully Qualified Name (Example: View.ColumnName)
43 47
44
-AdHocSettings.UseColumnNameForDashboardCommonFilters = False;
48
+##Global.asax (C♯)
45 49
46
- - Use 'ColumnName' Only
47
---------
50
+```csharp
51
+//Using the fully qualified name to determine common filters (Example: View.ColumnName)
52
+AdHocSettings.UseColumnNameForDashboardCommonFilters = true;
48 53
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;**
54
+//Using only the 'ColumnName' to determine common filters
55
+AdHocSettings.UseColumnNameForDashboardCommonFilters = false;
56
+```
50 57
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.
58
+##Global.asax (VB.NET)
52 59
53
-To enable datasource-specific behavior, fully qualified column names for dashboard filtering, in your deployment after upgrading:
60
+```visualbasic
61
+//Using the fully qualified name to determine common filters (Example: View.ColumnName)
62
+AdHocSettings.UseColumnNameForDashboardCommonFilters = True
54 63
55
-``AdHocSettings.UseColumnNameForDashboardCommonFilters = true;``
... ...
\ No newline at end of file
0
+//Using only the 'ColumnName' to determine common filters
1
+AdHocSettings.UseColumnNameForDashboardCommonFilters = False
2
+```
... ...
\ No newline at end of file