Why Two Users Might See Different Data in Omni Dashboards

Workbooks
1

When two users view the same dashboard but see different results, there may be differences in filters, cache, access controls, or time zone configurations. This article walks through each factor to help you diagnose and resolve discrepancies.

Filters

Dashboard filters are the first thing to check.
If filters are set differently between users, they’ll naturally get different query results.

Confirm that all filter values match exactly for both users.

Cache

Caching may lead to temporary differences in results if one user is served cached data and another runs a fresh query.

  • Run without cache: Try refreshing the dashboard with cache disabled to ensure you’re pulling the latest data from the database.
    See the Query Cache documentation.

  • Filter suggestion cache:
    Filter dropdowns use a suggestion cache that lasts 30 days by default. New values may not appear immediately, which can cause users to select different filters or think certain filters are missing.
    To make suggestion caches respect your dashboard’s cache policy, enable the filter_suggestions_must_obey_policy parameter at the model level.

Access

Attributes

Access filters and grants may lead to data differences when users don’t share the same user_attributes.

  • Access filters — These apply row-level filters

  • Access grants — These can restrict access to specific views or fields.

Check the user_attributes defined for both users and review whether any access_grants or access_filters are active in the views, topics, or models powering the dashboard.

Permissions

Even if both users can open the same dashboard, connection roles and database routing may differ:

Confirm both users are using the same database environment, schema, and warehouse.

Time Zones

Differences in time zone handling can shift date boundaries, affecting counts and aggregations.

Omni supports user-specific time zones if enabled at the connection level and passed through the omni_user_timezone attribute.

Check that both users’ effective time zones are the same.
If the org or connection is configured with “Do not convert,” date fields will remain in database time — which can explain discrepancies in day-level totals.

Summary

When users see different dashboard results, check the following in order:

  1. Filters — Confirm identical filter values.

  2. Cache — Refresh with cache disabled and verify suggestion cache behavior.

  3. Access — Compare user_attributes, access_grants, and connection roles.

  4. Time Zones — Align time zone settings across users.

Consistent settings across these four areas ensure your team sees the same, accurate and expected data.