Yes this must be some left-overs in the demo database from upgrades over the years. Please ignore this. I assume that in your local database you first load a dashboard, then the related items, so you should never read those orphaned items. I think its up the server / DHIS 2 to clean this up and the client should be robust enough to ignore them.
Yes that report actually exist. I can see it has publicaccess set to none. You probably access it by using the admin user or some other user which does not have the ALL authority and hence cannot see it.
This is a general problem in terms of cascading sharing - i.e. sharing the dashboard without giving access to the items in the dashboard. This is a general problem we need to solve on the server side and something you can ignore for now on the client side.
regards,
Lars
Is this normal behaviour? If yes, which rules should I follow when working with dashboard items?
Hi Lars,
not sure if it’s a demo database issue. Not sure if it’s the same, but it’s at least similar to what I reported as a bug some time ago: https://bugs.launchpad.net/dhis2/+bug/1415434
Yes this must be some left-overs in the demo database from upgrades over the years. Please ignore this. I assume that in your local database you first load a dashboard, then the related items, so you should never read those orphaned items. I think its up the server / DHIS 2 to clean this up and the client should be robust enough to ignore them.