5ef1345757438f483d2ab9a0207328179dfa5009
FAQ/force-update-results-on-report.md
| ... | ... | @@ -1,8 +1,19 @@ |
| 1 | -#How Do I Force a User to Click on 'Update Results' Before Showing Any Data? |
|
| 2 | 1 | |
| 3 | -To ensure a user must click on "Update Results" before showing any report data (regardless if there are filter parameters or not). |
|
| 2 | +##Question |
|
| 4 | 3 | |
| 5 | -Add the following to the _ReportViewer-Body.ascx_ file in the ``<script>`` tag at the very bottom: |
|
| 4 | +How Do I Force a User to Click on 'Update Results' Before Showing Any Data? |
|
| 5 | + |
|
| 6 | +##Answer |
|
| 7 | + |
|
| 8 | +There are actually two ways to get this functionality. |
|
| 9 | + |
|
| 10 | +###Method 1 |
|
| 11 | + |
|
| 12 | +If you are using filters in the report you want to force this functionality on, you can use the [[Filter tab|http://wiki.izenda.us/Guides/ReportDesign/5.0-Filters-tab#Require-[blank]-Parameters-in-Viewer]] controls to require a user to enter the filter parameters before ever displaying data. |
|
| 13 | + |
|
| 14 | +##Method 2 |
|
| 15 | + |
|
| 16 | +To ensure a user must click on "Update Results" before showing any report data (regardless if there are filter parameters or not), add the following to the _ReportViewer-Body.ascx_ file in the ``<script>`` tag at the very bottom. This will override a javascript method that normally runs : |
|
| 6 | 17 | |
| 7 | 18 | ```javascript |
| 8 | 19 | function GotReportViewerConfig(returnObj, id) { |