b1aa684f41f33166f1531a6afd27441d5def93f0
FAQ/force-update-results-on-report.md
| ... | ... | @@ -1,4 +1,3 @@ |
| 1 | - |
|
| 2 | 1 | ##Question |
| 3 | 2 | |
| 4 | 3 | How Do I Force a User to Click on 'Update Results' Before Showing Any Data? |
| ... | ... | @@ -11,9 +10,9 @@ There are actually two ways to get this functionality. |
| 11 | 10 | |
| 12 | 11 | 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 | 12 | |
| 14 | -##Method 2 |
|
| 13 | +###Method 2 |
|
| 15 | 14 | |
| 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 : |
|
| 15 | +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 when the page is loaded: |
|
| 17 | 16 | |
| 18 | 17 | ```javascript |
| 19 | 18 | function GotReportViewerConfig(returnObj, id) { |