50bee1eb3e06a57f03edce401d788a3a09c0472d
FAQ/applying-hidden-filters-programmatically.md
| ... | ... | @@ -93,4 +93,12 @@ Public Function FilterCanBeAddedToReport(jts As JoinedTableCollection, ByRef new |
| 93 | 93 | Next |
| 94 | 94 | Return toReturn |
| 95 | 95 | End Function |
| 96 | +``` |
|
| 97 | + |
|
| 98 | +##Stored Procedure Parameters |
|
| 99 | + |
|
| 100 | +The process for applying a hidden stored procedure parameter programmatically is slightly different, as the column name needs to be referenced differently. If you are using the column fullname, then this will be done automatically. But in order to do it manually, here is a snippet that would add a stored procedure parameter as a hidden filter in PreExecuteReportSet. Keep in mind that while a fully-qualified table name is not required, if there is more than one match found, a null reference exception will occur. |
|
| 101 | + |
|
| 102 | +```csharp |
|
| 103 | +reportSet.Filters.AddHidden(new Filter("[dbo].[CustOrderHist].[PARAM_CustomerID]") { Value = "BONAP" }); |
|
| 96 | 104 | ``` |
| ... | ... | \ No newline at end of file |