FAQ/Questions/reusing-filter-values-for-stored-procedures.md
... ...
@@ -42,7 +42,7 @@ public override void PreExecuteReportSet(ReportSet reportSet)
42 42
}
43 43
```
44 44
45
-#VB.NET example
45
+###VB.NET example
46 46
47 47
```visualbasic
48 48
Public Overrides Sub PreExecuteReportSet(ByVal reportSet As ReportSet)
... ...
@@ -71,4 +71,19 @@ Public Overrides Sub PreExecuteReportSet(ByVal reportSet As ReportSet)
71 71
End If
72 72
Next
73 73
End Sub
74
-```
... ...
\ No newline at end of file
0
+```
1
+
2
+###Screenshots
3
+
4
+Here is a screenshot of the expected setup for the filters in a report using two stored procedures with the same parameter(CustomerID) required to enable the report to execute successfully.
5
+
6
+![Stored Procedure Filters on CustomerID](/FAQ/Questions/setting-defaults-for-report-designer/sproc_filters.png)
7
+
8
+The key attributes to take into account are that both filters are for the CustomerID parameter and that the parameter with the value is marked with a checkmark in the box labeled "Param" denoting that the filter will be visible in the report viewer. The other filter will not be visible in the viewer.
9
+
10
+---
11
+
12
+On the report viewer, the report will only display a single filter but both filters will pass the validation check to ensure that all stored procedure parameter filters have a value. Keep in mind that this will only work if the columns are named the same. Therefore, attempting to filter on the CustomerID parameter and pass the filter value to another parameter named Customer_ID will not work, even if the parameters are synonymous.
13
+
14
+![Stored Procedure report with CustomerID filter](/FAQ/Questions/setting-defaults-for-report-designer/sproc_viewer.png)
15
+