Workset 1

[Anonymous]

Hi,

I have a question regarding the workset "Workset 1".

Why is everybody's saying that we must not rename or use this workset?

I know it can't be deteled, but why can't we use it? Seems like a big issue everywhere, but I don't find out why...

Thank you

[Karol_Piroska]

you must have some different Revit. I just tested this again on two test files to be 100% certain I'm not talking nonsense; and yes, you can use or rename the workset1 without issues.

[martijn_pater]

---

@Anonymous wrote:

I've been hanging out here for years and other forums too....I've never seen anyone suggest not using Workset1.  What are you supposed to use, Shared Levels and Grids?

---

I've seen it mentioned, but when someone says "Don't use Workset1" I think might just mean that it is better to rename your worksets to an office standard ie. But if your office standard is working in Workset1 that should be fine... It might become confusing when you insert a linked file on the host Workset 1, because then when you hide Workset1 you hide the entire link aswell. If you insert your linked file on its own 'Workset_link' and then hide Workset1 it works as expected (if you didn't expect the link to get hidden on the workset it was placed on to begin with). It does not matter how you name them, if they are named the same it will hide them in the host file aswell as in the link. If you don't want the linked file to be influenced (as someone else might have just used the Workset1 standard), you would just rename your own Workset1.

[ToanDN]

One thing to keep in mind is that Workset 1 cannot be deleted.

[VascoP]

I have been renaming Workset1 since 2019, and it works very well, it's the solution to all the problems mentioned above in this thread (because some of the problems that existed before are no longer an issue). You can hide anything from any link that way. Because each link (internal or external) has a different workset name.

Keeping Workset1 in the file without any elements is also an error in my opinion because you will be spending hours, for as long as the project lasts, 'cleaning up' elements from workset 1. How can we use worksets properly if you can never trust Workset 1 to be clean? (unless you are the only person working in the file and you never forget to place elements in the correct workset)
I tested the statement below back then (2019), and I tested it again now and it works fine with me. I have been using it for a while (and made it a standard in the office to rename it) - this hasn't been an issue for years. Is there anyone still experiencing this? (in versions 2020  or newer)

"...if you rename Workset1 it will still turn itself off in the link when the host workset1 is switched off, even if the names are different. " - not any more??

[JAguiling73FX6]

It only reacts as if it were "Layer 0" ONLY if it was kept as "Workset1" and you were globally turning off worksets.... If you rename it to something else, it no longer links and associates itself to any parameters named the same in the link, even if they originated as "Workset1"  If visibility controls were established either by View or View Template, and not globally, then those are settings that are being controlled on a micro level, in which it doesn't matter what those worksets are renamed to.  You can indeed control the links visibility via worksets if the workset name matches between the link and your model, but if "Workset1" is renamed in either your model or the link, then you should be fine.  It works the same as Phases and Phase Filters, if the defaults are unchanged, it has special properties to match it's links visibility in certain ways, once Phases and Phase Filters are renamed, then those visibility properties that get linked are then detached.