Nested Family with Shared Generic annotation Yes/No in text instead of checkbox

[mlvau]

Hi all,

I hope you're all doing well. I was wondering if you could lend me a hand with an issue that I am having.

Essentially I want to create a checklist. Here's what I have in mind:

- Our designers will mark each task from the checklist as they complete it.

- Once all tasks on a specific sheet are finished, the text,lines,etc associated with them will disappear.

- The task are listed in a note block schedule, allowing the project leader to easily check them on/off which out going through all the sheets manually.

I've already started working on it and testing things out, but I'm not completely satisfied with the outcome just yet. (You can see what I've built by opening "TEST_PROJECT.rvt".)

While exploring solutions, I came across this link: https://forums.autodesk.com/t5/revit-architecture-forum/self-populating-schedule/m-p/9596013

I believe it's a neater version of what I'm trying to achieve. I made some modifications to the family, making a shared version and then I nested it into another generic annotation family to group the tasks together.

The issue I find is that once the shared family is nested and then scheduled the family that are nested show up with the Yes/No statement instead of the graphical checkbox.

Do you think there's a way to make it appear as an interactive checkbox that can be toggled on and off? I want to make sure all three aspects mentioned above work seamlessly.

Thank you so much for your help and support!

[TripleM-Dev.net · Accepted solution]

Hi @mlvau,

The Yes/No parameter shows as text because they are "read-only", they can't be edited at that 'level'.

For this case it is because it's a shared family (similar to instance parameters for elements in groups), only Project parameters could be directly editable (can't be added to Generic annotation and can't drive geometry in family)

Options:

1. Don't use the families nested

2. If it's a fixed number of nested families (or limited number), link the instance parameters of the shared nested family to the main family parameters and schedule the main family (will then be columns and not rows), in the properties panel the various tasks checks would be listed as "rows"...

- Michel

[mlvau]

Hi Michel,

Thank you for taking the time to reply.

With option 2 I don't 100% understand. What you saying that even though I'll have multiple parameters in different columns and can't rearrange them as rows? I have attached a screenshot.

Also what are your thoughts about visibility, that once the task is done it hides automatically.
I can do that individually with a formula that once the task is done then the visibility parameter but then you never see the "X" because it hides it straight away. I guess that can be ok just wanted to see if you had an opinion on that.

Thanks 🙂