Announcements
Welcome to the Revit Ideas Board! Before posting, please read the helpful tips here. Thank you for your Ideas!
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Create a Key Schedule for more than one category

Create a Key Schedule for more than one category

Create a Key Schedule for more than one category

Purpose

Some times the same key schedule information needs to be shared between different categories (pipes + fittings)

It will reduce number of Key Schedules and usability of data adding (for example, use Tab for pipe + fittings highlight and choose one Key for different categories)

10 Comments

Would adding shared parameters to key schedules solve the issue?

karol.wozniak
Contributor

Hello,

If I understand correctly, we came across a similar problem. I will explain in short:

We have two parameters for floor finishes (Primary and Secondary) as Room parameters. Currently, the Floor Finish parameter is the built-in one, while we add the Secondary Floor Finish parameter. Both 'text' based.

Ideally both fields (parameters) would be populated using the same Key Schedule. Key Schedule allows us to store additional information regarding the finishes (like LRV used), as well as restricts the user input to pre-defined entries. Also, the end-goal is to export the LRVs per room for all the finishes used and perform contrast analysis against a pre-set rules (probably in Excel, this work is ongoing).

Is there any way to populate two parameters from the same Key Schedule? Or maybe there is an alternative workflow?

We did consider materials (and split faces), but these do not schedule per room on a floor for instance (please, correct me, if I am wrong here).

If we had the ability to apply a Multi Category Key schedule across select elements, I.e. Project information, Areas, Rooms, etc. We could incorporate Global information like CODE (IRC, NFPA, etc) globally to elements for scheduling and calculations. This would strongly cast element types or instances to associated data and allow for integral checks and validations within revit.

RonAllen_WareMalcombcom_0-1663718553175.png

 

aweiss-RD-STR
Explorer

Hell yeah!

the only issue that multi category schedule is not fully including all the instances in the projects 

some builtin families can’t be multi-category scheduled 

 

Autodesk - pleas open the flush gate

CharlesBerteaux
Advisor

Such a great idea! 

Joey_JM
Advocate

This would be great for managing codes/abbreviations that are common across several categories.

 

@kimberly_fuhrman-jones  can the following idea be merged with this?:

https://forums.autodesk.com/t5/revit-ideas/create-a-key-schedule-for-more-than-one-category/idi-p/65...

 

@Joey_JM @good find! Funny I had a post on there from 2016- how things have changed!

 

@Joey_JM , sure! Thank you for the suggestion!

adariz76
Explorer

Great Idea to have the possibility to create key-schedules for more than one category. As it is possible also for parameters to add categories where they should applied, you should implement this even for key-schedules.

 

Would be also nice to have the possibility to move a key-parameter to a different group then "ID-DATA".

juho_haikio
Contributor

I fully agree with this proposal. From an architectural perspective, the same key schedule information is very often shared between closely related categories such as doors and windows. Splitting identical data into separate key schedules only creates unnecessary duplication, increases maintenance effort, and risks inconsistencies in the model.

What makes this especially frustrating is that this idea was originally proposed already in 2016. It is disappointing that such a fundamental usability issue has still not been addressed by Autodesk. Key Schedules are a core data-management feature, yet their limitations suggest that development priorities are driven more by popularity or “vote counts” than by a real understanding of everyday BIM workflows.

It is genuinely irritating that commonly needed, productivity-critical functionality like this remains missing after so many years, despite being very clearly relevant to real-world use.

Can't find what you're looking for? Ask the community or share your knowledge.

Submit Idea