Dashboard saving - Error - After upgrade to 2.40.x - Any thing changed?

jthomas · 28 July 2025 09:05

Hello all,

We are getting an error - after upgrading. It seems all charts now needs to have an explicit sharing settings to get the dashboard saved for non-super users..

Previously we could create charts and (no specific settings to charts) and place in dashboard and share it to a usergroup - this was enough for all in the usergroup to edit/save.

But now in 2.40.8.2 we get the below error

Because one of the chart was not explicity shared

Gassim · 29 July 2025 15:22

Hi @jthomas

Yes, you spotted the change for version 2.40 and above. As mentioned in the v2.40 upgrade notes:

When updating a Dashboard, user is required to have METADATA_WRITE permission to the Dashboard itself and METADATA_READ permission to all referenced objects in all DashboardItems. Administrators can use cascade sharing in order to grant required sharing permissions when needed.

github.com/dhis2/dhis2-releases

releases/2.40/README.md

master

# 2.40 Upgrade Notes

> :warning: **Please ensure you have read the upgrade notes from the [PREVIOUS RELEASE](../2.39/README.md), if upgrading from an earlier version**

## Update Dashboard

- When updating a `Dashboard`, user is required to have `METADATA_WRITE` permission to the `Dashboard` itself and `METADATA_READ` permission to all referenced objects in all `DashboardItems`. Administrators can use [cascade sharing](https://docs.dhis2.org/en/use/user-guides/dhis-core-version-master/analysing-data/dashboards.html#cascade-sharing-of-visualizations-on-the-dashboard) in order to grant required sharing permissions when needed.

## Line Listing/Analytics

The dates related to the time dimension "Last updated on" will also take into consideration the last updated date used by mobile or other API clients. Basically, the rule being applied is: if there is a "last updated" date persisted by the client/mobile, this date will take precedence in analytics queries, and will be used by the "Last updated on" dimension. Otherwise, it will use the default/usual server-side "last updated" date.

The time dimension "Event date", which represents the execution date and can assume different names depending on the program/stage (e.g. "Report date", "Event date", "Visit date", etc.), will now display the timestamp along with the date. This will give more precision to the client/mobile applications if needed. If no timestamp is set, it will be displayed with zeros.

## API

- From 2.40 onwards the `attributeValues` property in the `/gist` API is a object map with the attribute IDs as keys and the plain values as values. Further properties of the attribute will no longer be included in the values.

- A new column `ounamehierarchy` was added to events and enrollments analytics tables. A full export of analytics tables is required in order to make analytics queries work correctly, for events and enrollments.

This file has been truncated. show original

I hope that you are able to resolve this easily, please keep us updated!

Thanks!

jthomas · 30 July 2025 11:10

Wow Thanks a million @Gassim