1 of 1 people found this helpful
are you talking about custom workbooks that have been published or custom views that clients have saved? I think it's the latter and we haven't found any method for deleting these, but if you submit an idea, we can vote it up. Ideas
I am talking about the latter, and we have almost 15K of them. I would bet $1 that almost 14,915 of them have never been used since their creation.
Idea submitted: https://community.tableau.com/ideas/6233
Thanks for this! While it's not exactly what I was looking for, I definitely want to use it.
Especially as our catalog grows over 1,400 visuals, the need for identifying stale and unused visuals is growing commensurately.
I just checked, we have 19,937 custom views. But I'm under the belief that the large quantity doesn't adversely affect performance as they are stored as named value metadata within the PG database. And I've confirmed this within dev by just publishing a few of our long running workbooks to a clean environment and there isn't a difference in rendering.
Thanks for checking that, Jeff.
I'm not as concerned about performance as I am about the sheer volume of customs that exist. Our front-end displays a tile for each custom created by our users. If they are not made public, they only appear in that particular user's display, but anything that is public adds to the list that everyone can see.
It isn't causing any active client noise, but I see it becoming a greater reality as we continue to add clients.
Does the REST API include anything I could use for this?
I don't see anything in the REST API reference. https://onlinehelp.tableau.com/current/api/rest_api/en-us/help.htm#REST/rest_api_ref.htm#API_Reference%3FTocPath%3DAPI%2…
Good point on the front-end. What does your front-end look like? We also have a front-end, but we only show the private custom views for the specific user.