I agree. Thanks for the Idea!

Hi Andy,  My team and I feel exactly the same way.  It really puts a damper on the new update. 

Yes agreed. It feels counterintuitive to the user experience.

Now that it is that has been changed, "the grass is always greener", when I have my people open a project from the home screen(one level down), they get very confused because at the moment at least, there are no generic workbooks that relate to Service as a whole. There are only two projects that have multiple workbooks.

Hi Andy Miller,

Upgrade to tableau server 10.5.1 & it should work now.

10.5.1 will default to workbooks rather than nested folder.

ram b wrote:

 

Hi Andy Miller,

 

Upgrade to tableau server 10.5.1 & it should work now.

10.5.1 will default to workbooks rather than nested folder.

Confirmed on our 10.5.1 install.

Hey Toby - do you get the opposite behaviour as described by Kord above... ie if the project has only nested projects and no workbooks, do you now get an empty screen, since there are no workbooks..?

No, you will see the Projects.

When I click on the "Development" project:

I created a dummy child project in my Default folder

and when I click on the Default project, Workbooks is the default view, not the Projects page with the sub-project

So there appears to be no "intelligence", the default view is fixed, thus I can only guess they switched the default view from Projects to Workbooks.  So it doesn't appear to act in a format that we're conditioned to, at least in the Windows file manager sense

Thanks for the update and the screen shots :-)

I have the same issue, driving me mad. Did you figure out how to change the default to Projects when your workbooks section is empty?

Hi Josiah

I don't think there is a way for you to change the behaviour.

I suggest you vote on this idea https://community.tableau.com/ideas/8469  which has been bourne out of various discussions on the behaviour on server since nested projects were introduced.

Donna

This happens when the product manager and the developer are not users. There are no proper usability tests and you just improvise based on customer feedback without really thinking things out thoroughly.

The real solution here is to merge Projects and Workbooks into a single thing called "Content" and behave just as file systems has worked for decades and with what the entire world is familiar with.

We have around 2000 workbook, we tried to reorganize them using sub-projects, and either being "Projects" or "Workbooks" the default view, navigation is so **** confusing for the majority of people, that we decided to stay with the old flat root folders structure. It's a shame.