Hi, I just discovered that when we hide a screen in the layout, this disables the content of the “Find Use” view in the database.
This can lead to delete many columns by error… as I just did 
Just sharing so that others don’t make the same mistake.
Screen: hidden

=> “Find use”: empty
=> If Screen turned into visible → “Find use”: filled
Just curious, in which cases would you want to hide a tab and then make it visible later?
for example for backup screens, or work in progress etc
1 Like
Is there a reason you don’t use publishing control?
I’ve done this for a few cases where you might have a screen (tab) that’s only shown as a result of completing an action sequence.
E.g. submit a form, route to a hidden “thank you” screen.
2 Likes
MattLB
6
Was this ever addressed? Find uses should find all uses: hidden screens or not.
I know they ‘find uses’ when a componenet is hidden - so why not a screen?
Thanks