Item type not supported or undefined is a message displayed on the dashboard when references of an item are removed from the user account. It happens in other areas of the system as well, for example, with program stages.
We have attempted to demystify this on our solutions page here. I hope you find this article useful.
My question is more on maintenance related aspects. Has anyone created a check that looks at Dashboards access and can give errors when users (within user groups) have access to a dashboard and also do not have access to all of the objects within that dashboard? Based on the nested nature (users–>userGroups, objects–>dashboardItems–>dashboards), I’m a bit daunted by the prospect of creating a SQLView…but perhaps this is the best/only way to go about it?
I’m also wondering if a feature request could possibly warn/prevent this from happening in the first place (i.e. when giving edit access to users that don’t have access to the objects, provide a warning) or second place (if you are a user who is about to/in the process of editing a dashboard, give a warning if they do not have access to objects) or third place (once this happens, at least allow for the object to be brought back, be discoverable, be pulled, edited, and pushed back with proper access)