Worksets Hopping About a Bit?

When using a workshared file, we've found that on occasion, the active workset seems to change itself for no apparent reason. This particular quirk has always stumped us. Recently however, we have got to the bottom of this. I'm not entirely sure if this is a bug or by design, but the following is the behaviour that causes this to happen

In this scenario. Worksharing is enabled and 'Workset1' & 'Shared Levels and Grids' are created automatically. In addition, I have added a workset called 'A'

'Workset1' is the active workset. Note the following rules:

• On opening the workset dialogue, the Active Workset combo box always has initial focus
• The Active Workset combo box can only be populated by open worksets

Now we decide that we want to close 'Workset1'. On leaving the Workset dialogue, everything is normal and 'Workset1' is still listed in the main Active Workset box at the bottom of the main screen

Now we want to re-open 'Workset1', so we go to the workset dialogue. Under the two rules above, Revit jumps straight to the active workset combo box and says "Hang on, 'Workset1' isn't open, so it's not in the list. Therefore I will leap quick smart to the first entry in the list, in this case 'A'". 

Because the user's focus is on re-opening 'Workset1' in the table below, this sleight of hand by Revit is easily missed, resulting in the following

So the moral of the story is to remember to set back the active workset immediately after. Hope this helps

When Shared Parameters Lose their Way

On occasion, a shared parameter that is under one group in a family will mysteriously end up in the 'Other' group, when loaded into a project. In this case,the parameter 'Section Name'

In order to fix this, do the following:

• On the 'Manage' tab, click 'Project Parameters' on the 'Settings' panel
  
  
• Now select the shared parameter from the shared parameter file and set the 'group under' to the match the correct group in the family. Click 'Ok'

• Now go back into the Project Parameter dialogue, select the parameter and hit 'remove'
  

• Now you'll be left with the shared parameter in the family under the correct group
  

I've no idea why Revit does this, but its clearly a bug. It will do it with the same shared parameter used in multiple families, but once you apply this fix, all the families that contain the offending parameter will then be correct.