Restrict usable families' categories in Worksets

[giuliodenonno]

Hi,

Is there a way to preset Worksets so that they can host only certain families' categories and won't allow to model other unwanted categories within them?

Or in other words: is it possible to set a workset in order to show an error message when someone tries to model a family category that is not meant to be modeled in that Workset; an error message like: "The settings of the current Workset do not allow to model XXX Family Category within it. Please change workset or edit the settings of the current workset in order to add this category of family in the model."

Or any other similar strategy to achieve this.

Thanks in advance,

Giulio

[ToanDN]

No.

Add the restriction to the family name.

[JasonKunkel]

It wouldn't be dynamic, but you could do it post. I think a Model Checker check could be written to look for certain categories and check the Workset name and report anything that doesn't match what you want.

[lucdoucet_msdl]

@giuliodenonno 

An alternate approach to alerting the user immediately in their modeling session would be to monitor on a weekly or daily basis with a dynamo script set to identify a set of families on the wrong worksets and advise them by your choice of communications (ex. Phone, email, excel list, etc).

Hope this helps,

-luc

[giuliodenonno]

Thank you all for your contributions.

@lucdoucet_msdl your suggestion helps but doesn't solve my issue unfortunately.

I would like to have a way to solve this problem upstream once for all as the monitoring and checking activity is still time consuming: would prefer avoiding it if that was possible. 

Giulio

[ToanDN]

---

@giuliodenonno wrote:

I would like to have a way to solve this problem upstream once for all as the monitoring and checking activity is still time consuming: would prefer avoiding it if that was possible. 

Giulio

---

- You can learn API / macro to create different insert buttons to Revit interface that only insert families to a certain workset

- Dynamo can be an after-the-fact solution, meaning you run the script to re-organize families to worksets after families already placed

- 

[lucdoucet_msdl]

---

@giuliodenonno  a écrit :

I would like to have a way to solve this problem upstream once for all as the monitoring and checking activity is still time consuming: would prefer avoiding it if that was possible. 

---

Hard to achieve a balance between policing standards and preventing violations as it will always depend on the people and politics of the work environment.

This said, could you gives us an idea as to why the restricting of family types versus worksets is being implemented  in your case? This could allow you to rethink alternatives that bypass the problem.

-luc