Saving data filter settings using Views

Saved report views let you reuse the same reporting filters and chart settings without rebuilding them each time.

Report views are shared between the Usage and Performance pages.

They are separate from Management views.

Where report views are available

Report views are available on:

• Usage
• Performance

They are not shown on:

• Overview
• Management

Management has its own separate view system for table filters and configuration.

Open the report views menu

Select the eye icon beside the shared report filters.

The menu shows:

• existing saved views;
• a delete icon beside each saved view;
• Save as new view.

Open a saved view

Select a saved view from the menu.

The app applies the settings stored in that view to the current report.

A view created on Usage can also be opened from Performance, and a view created on Performance can be opened from Usage.

This works because both pages use the same shared report-view system.

What a report view stores

A saved report view stores the shared reporting filters:

• time period;
• brand;
• group;
• agent;
• ticket form;
• included macro tags;
• excluded macro tags.

It also stores Usage-specific chart settings:

• Total Macros Usage Timeline grouping by day, week, or month;
• Total Macros Usage by Attributes over Time entity type and time grouping;
• Individual Macros Usage by Attributes entity type;
• Individual Macros Usage over Time grouping by day, week, or month.

Performance-specific Drill-In settings are not saved.

For example, chart grouping selected inside an expanded macro row is reloaded when Drill-In is reopened.

Save the current setup as a new view

1. Configure the report filters.
2. Configure any Usage chart settings you want to preserve.
3. Select the eye icon.
4. Select Save as new view.
5. Enter a name.
6. Select Save.

The view name is required.

Change an existing view

Existing report views cannot currently be renamed or updated.

To preserve changes made after opening a view:

1. Open the existing view.
2. Change the filters or chart settings.
3. Select Save as new view.
4. Enter a new name.
5. Save the new view.
6. Delete the old view when it is no longer needed.

Do not assume that changing filters automatically updates the opened view.

Delete a saved view

1. Open the report views menu.
2. Find the view you want to remove.
3. Select the trash icon beside it.
4. Confirm the deletion if prompted.

Deleting a view removes the saved configuration. It does not delete or change any Zendesk data.

View names and limits

The current interface:

• requires a view name;
• does not require names to be unique;
• does not show a limit on the number of saved views.

Using distinct, descriptive names is still recommended.

For example:

• Last 30 days - Support groups
• Enterprise brand performance
• Exclude internal macros
• Weekly adoption review

Duplicate names can make the menu difficult to use.

Who can access report views

Report views are stored at the Pythia client or account level rather than for an individual Zendesk user.

This means they should be treated as shared account views, not private personal views.

Use names that other administrators can understand.

Missing brands, groups, agents, or forms

A saved view can reference a Zendesk brand, group, agent, or ticket form that is later removed or becomes unavailable.

When this happens:

• the stored value may still be sent in report queries;
• the filter may not display a readable matching label;
• the report may return no results.

Macro tags are stored as text values. A tag that is no longer used can remain in the saved view and return no matching data.

When an old view looks blank or produces no results:

1. Open the shared filters.
2. Review each selected value.
3. Replace missing or outdated selections.
4. Save the corrected setup as a new view.
5. Delete the old view.

Saved views and refresh behaviour

Shared report filters reset after a page refresh unless they are reopened from a saved view.

They can also reset when you leave the shared Usage and Performance report route.

Use saved views for report configurations that need to be reused across sessions.