Chart filter not working for non-admin users in 2.0.10

* Describe the bug

In version 2.0.10, chart filters are not working for non-admin users.
When a non-admin user applies a filter to a chart, the chart data does not update according to the selected filter conditions. However, the same filter works correctly when logged in as an admin user.


* Environment

  • NocoBase version: 2.0.10
  • Database type and version: PostgreSQL 16
  • OS: macOS Tahoe
  • **Deployment Methods:**Docker
  • Docker image version: nocobase/nocobase:2.0.10
  • NodeJS version: v18.19.1

* How To Reproduce

  1. Log in as an admin user.
  2. Create or open a page containing a chart block.
  3. Configure a filter for the chart.
  4. Create a non-admin role with limited permissions.
  5. Assign the role to a test user.
  6. Log in as the non-admin user.
  7. Attempt to use the same chart filter.

Expected behavior

Non-admin users should be able to use chart filters normally, and the chart data should update according to the selected filter conditions, as it does for admin users.


Note

This issue happens in the Classic Version (v1).


Logs

N/A

@hongboji - Can you please check this. It’s impacting our users as they are not able to view accurate info in the dashboards.

Please reproduce this problem in the demo environment.
https://a_8hwne7u84ho.v13.demo.nocobase.com/admin/
(NocoBase default username and password)

https://a_8hwne7u84ho.v13.demo.nocobase.com/admin/qqsqa98uehp

Steps to reproduce

  1. Login as admin
  2. Navigate to Testing Issue → Filter Issue
  3. Select the priority and click on filter.
    Observe that the filter works correctly

Repeat the same steps with Sales role

Observe that the filter doesn’t work correctly

The issue only happens when there are access controls set at the table. In this case, we have set Individual permissions for Ticket table and also added a custom Data scope. Refer to the screenshots below

Hello!
Thank you for reporting the issue. Please wait while we fix it.
You can use the v2 version page; v2 is correct.

1 Like

Thanks for confirming. Could you please reply to this thread once the issue is fixed?