Switching data sources collapses the tree view in navigation

A fix for this issue has been implemented in version 2025.2.28.0
Implemented

Switching data sources collapses the tree view in navigation

avatar

Hello,

until now we only used a single data source - an SQL server. Now I started to play around with Hub Business and integrated it in my RDM.

After I added the Hub Business I switched back to my SQL data source and all my folders in my user vault were collapsed...!!!

You already remember the view somewhere as after every RDM start they are as I left them. Please extend this also when switching data sources. I hate it, when I have to rebuild my personal default view every time I switch data sources...

Thanks a lot for your help!

Brgds Andreas

All Comments (5)

avatar

Hello Andreas,

I reproduced on my end as well, I think it might be a bug, I feel like it worked previously. I've opened a ticket so we can investigate.

It's not a perfect workaround, but if you right click in your user vault, you can do "expand all", which might make things easier than expanding them manually. Though, of course, if there's folders you don't want expanded, you'll have to wait for us to fix the bug as I don't think there's a workaround for that.

Regards,

Hubert Mireault

avatar

Hello Hubert,

thanks a lot for your quick reply! Just in case before someone asks - I use 2025.2.27...

it does not happen when switching between vault, user vault, etc. only when switching data sources.

Edit: I know this, but i have a few levels of subfolders and I don´t want to have them all expanded...

Brgds Andreas

avatar

No problem, I wanted to mention the possibility in case you weren't aware, but I understand the annoyance when there's multiple subfolder structures and you don't want them all expanded.

We've assigned this to a developer and hopefully we're able to find a solution quickly.

Regards,

Hubert Mireault

avatar

Hello Hubert,

Fixed with 2025.2.28.0 - Thanks!

Brgds Andreas

avatar

I'm glad to hear it now works for you.

Regards,

Hubert Mireault

A fix for this issue has been implemented in version 2025.2.28.0