Schedule data views for dependable operational reporting

Scheduled data views deliver a saved view on a repeatable timetable. They are useful for weekly account reviews, shift handoffs, and workload checks where people need the same evidence without rebuilding a report. Each delivery is a snapshot: use the live view when you need the current case state.

Prepare the view and audience  ·  Create or update the schedule  ·  Verify the first run  ·  Example: a weekly account review  ·  Design the report before choosing its schedule  ·  Read History as evidence of a run, then inspect the output  ·  Common problems

Prepare the view and audience

First open the underlying data view and confirm its filters, columns, and scope. Make sure its results answer a useful operational question. Your role must allow schedule editing; permission to see a view does not necessarily allow you to schedule it.

Create or update the schedule

1. Open Scheduled Data Views from reporting and select the schedule to edit, or start a new schedule using the available add action.
2. Select the Data View. Each schedule selects one view. Add data view opens the shared editor to create a saved view; return and select that view for the schedule. Check its columns and scope.
3. Choose the required export format: PDF for a readable snapshot or Spreadsheet (XLS) for subsequent analysis. Do not assume this schedule produces CSV.
4. Choose the agent recipients and review any additional email recipients. Remove addresses that no longer need the report.
5. Set the recurrence and start date/time. The choices include Once / send now, Every day, Every weekday, each individual weekday, and First day of every month. For Once / send now, start date and time are ignored and the saved occurrence is due now and the scheduled worker processes it on its next pass. Report generation and inbox delivery are separate outcomes; inspect History and confirm intended receipt. Recurring start times use the schedule’s stored timezone, which may differ from the recipient’s timezone. Choose the option shown in your editor rather than assuming an arbitrary cron-style schedule is supported.
6. Set Enabled appropriately and choose Update schedule. Reopen the schedule to verify the saved view, format, recurrence, start time, and recipients.

Verify the first run

1. For a one-time run, choose Once / send now, confirm Enabled and a small recipient list, then select Update schedule. There is no separate test button. Alternatively, wait for the configured first recurring occurrence. Do not send test output to a broad distribution list.
2. Inspect schedule history. Confirm that the run you are checking corresponds to the intended time and schedule.
3. Download the generated report from history and check its rows, columns, formatting, and customer scope. Compare a small number of cases with the underlying view.
4. Review the recorded recipients and confirm receipt with the intended report owner. A schedule saved successfully is not, by itself, proof that a recipient received an email.
5. If people in different regions depend on the report, verify the effective displayed start time and actual delivery before promising a particular local time.

Example: a weekly account review

Review the schedule when an account owner changes, a queue is reorganized, or a view definition changes. A technically successful report can still be operationally wrong if it answers last quarter’s question.

Design the report before choosing its schedule

A schedule answers when and to whom; the data view answers what. Treat both as part of one operational commitment. Before creating a weekly customer review report, write down its audience, the question it must answer, the point in the review process when it is needed, and who investigates a missed delivery.

These are design choices, not built-in defaults. Use the editor’s supported recurrence and verify the stored time zone rather than assuming every recipient sees the same local time.

Read History as evidence of a run, then inspect the output

After the first run, open History and locate the matching occurrence. Check when it ran, its recorded recipients and the downloadable report. Open the file and compare representative rows with the saved data view, allowing for cases that changed after generation. Look for missing columns, a wrong company scope, misleading date ranges and unexpectedly large output.

If History contains the expected run but an inbox has no email, investigate delivery separately from generation. If no run exists, recheck Enabled, recurrence and start settings before changing mail addresses. If the output is wrong, correct the underlying view carefully: other schedules may use it.

Revisit the schedule when a customer owner changes, a team reorganizes or the meeting stops. An unattended export can keep distributing information long after its original purpose has ended. Use the supported Enabled control and verify the saved schedule when pausing distribution.

Common problems

Continue learning

• Design useful operational views
• Configure data-view criteria and exports
• Use KPI scorecards alongside case reports