Shared nested families..."Parameter cannot be set by key schedule" error

Shared nested families..."Parameter cannot be set by key schedule" error

trevor.clarkM88RA
Enthusiast Enthusiast
818 Views
4 Replies
Message 1 of 5

Shared nested families..."Parameter cannot be set by key schedule" error

trevor.clarkM88RA
Enthusiast
Enthusiast

New to Revit 2022 is including Shared Parameters in key schedules but I'm bumping into an error "Parameter cannot be set by key schedule" for nested, shared family.

 

What's working: The basic HM doors/frames, the door type is set by a shared integer parameter (yay 2022!) with a key schedule assigning a door schedule (F, G, etc) linked to numbers.  In the family, a nested door panel family type is set with an if statement to the number to show, flush, half lite, etc. User picks the door based on the Key Name and everything updates. So far, looks good.

What doesn't work: Storefront needs to be window family to be correctly tagged and controlled graphically. We can't use Revit curtainwall, too many issues. For doors in storefront, we have nested, shared door family with identifical features/parameters as the above doors. However, in trying to control the shared integer parameter by key schedule, Revit gives the above error and will not set the number per the key schedule.

 

The only reference to this I can find online is the Revit 2022 Enhancements lists notes: Added an icon and tooltip in element properties for all parameters included in an assigned key schedule, which indicates the status: 'Parameter set by key schedule' or 'Parameter cannot be set by key schedule'.

 

Any help on getting the key schedule working for the nested family is much appreciated!

Follow-up: Could be a nested family conflict, not a key schedule conflict.

Further investigation may be that I understand nested families less than I thought - I'm finding that instance-based parameters in the nested family are grayed out when they're made in the nested family. Project made parameters for that category operate just fine, but the moment I put that same parameter into the nested family do some operation, Revit grays them out.

0 Likes
Accepted solutions (1)
819 Views
4 Replies
Replies (4)
Message 2 of 5

trevor.clarkM88RA
Enthusiast
Enthusiast

Follow-up: Could be a nested family conflict, not a key schedule conflict.

Further investigation may be that I understand nested families less than I thought - I'm finding that instance-based parameters in the nested family are grayed out when they're made in the nested family. Project made parameters for that category operate just fine, but the moment I put that same parameter into the nested family do some operation, Revit grays them out.

0 Likes
Message 3 of 5

ToanDN
Consultant
Consultant
Accepted solution

You need to associate the nested families parameters with parameters in the parent family in order to expose them to be recognized by the project key schedule.

0 Likes
Message 4 of 5

trevor.clarkM88RA
Enthusiast
Enthusiast

It definitely works, but creates some oddities due to mixing Door and Window categories. The nested door parameters are associated into a window family, requiring a Window key schedule to control and setting the integer parameter as both doors and windows, so it will appear at every window, even those without a door. Probably most tricky for users is the Door key schedule is still there for the typical doors, so the nested doors show it too but it doesn't work; users will need to click away from the nested family which contains most of the data (hardware, material, etc) and set the door type via the window family.

 

It seems a bit too Rube Goldberg for nested doors, but maybe it would work better in another application.

0 Likes
Message 5 of 5

ToanDN
Consultant
Consultant

You can change the window families to door category so you can control them using the same key schedule.  You can  still schedule window 'doors' and door 'doors' separately using schedule filters (by Assembly Name or whatnot).

0 Likes