01. Overview
We use this feature for the convenience of our users. Many times, a user is the first "unlucky" person to open a view, having to wait five or more minutes for the view to refresh before opening. The Task "View Update" is that last logical choice after moving data into Notes.
The Data Mover opens all views listed in the View Update Task, in the Views field. It does this just as a user would do, opening the view. The more views that are chosen, the longer the Data Mover will run, and the more disk space that will be used. The users will be thrilled to not have to wait.
02. Sample Uses
02.01. Run overnight to refresh databases whose views have been configured to not refresh automatically due to their large size.
02.02. Run after data integration tasks have been performed to ensure that the next user to open a view doesn't get stuck waiting a long time.
03. Task Specifics
03.01. If no view names are entered, Data Mover updates all views, including hidden views, in the database. Because of size issues and time issues, we recommend explicitly listing all views to open in the database.
03.02. The views are referenced by their alias name, not the common name.
03.03. View Update requires one Task document for all the views in a database. If this becomes cumbersome with multiple databases, hook them together using a Set (or schedule) form. |