I have a custom application and tried to add a dashboard for one of the tables. After some experiments I realized that I don't need that dashboard but seems can't delete it because of recursive limitations.
If I'm trying to delete that dashboard there is a warning of depencies, which says about presence of the dashboard in the application.
It's true, there is such connection. So, I go to the application designer and try to delete it. Actually there is a list where you have to uncheck the unnecessary dashboard.
And here is the trick. I can't turn off that single dashboard from the table's components because of warning that at least one item must be marked.
The deal is just in this limitation, not in the certain 'broken' dashboard. I can freely create another dashboard and delete it just after that. Or, as it will be automatically added to the component list, I can unlock the 'old' dashboard and delete it. But there will be always the last one dashboard that I wish to delete but can't release it from the app dependency.
Thus, I suppose I'm not only stuck with this unused dashboard but will not be able to delete the related table too. I'd like not having extra trash in my solution even if it's not seen for the users.
Is there a way to solve this puzzle or I've stepped on a core bug?
