Thanks for your submission and votes on this idea! We are evaluating where this request falls into our roadmap and will provide an update when we have made a decision.
This would be very helpful for many things, especially with the ability to show calculated parameters in tags. Key schedules are great for standardizing information, but often that information needs to be displayed outside a schedule.
Finish groups in apartment complexes
Occupancy types for rooms and areas (Assembly, /Occupant or /Unit text to a tag, etc.)
Abbreviated names of rooms or spaces
Anonymous
10-04-201610:49 AM
10-04-201610:49 AM
Expanding on this: can we have the ability to revise instantly the shared parameters themselves without third party apps?
Adding the ability to include calculated values in tags feels like a near miss when we still do not have the ability to use shared parameters in key schedules.
Anonymous
10-14-201604:17 AM
10-14-201604:17 AM
Question: if the Shared Parameter is defined in a Family, and also in a Schedule Key, which one wins?
There is no race, shared parameters can't be accessed in key schedules in any form. That is the issue.
Kyle Swanson Sent from Mobile Device
Anonymous
10-18-201610:45 AM
10-18-201610:45 AM
I submitted this idea as well. Having the ability to use Shared Parameters in a Key Schedule is a must. Calculated Values to Tags is pretty useless without enabling this feature.
Adding my support for this one. Was excited to use a calculated value in a tag, for occupancy calculations, but without the ability to tie it to the occupancy load factors in my key schedule - no can do Thanks!
@Anonymous First of all the issue of what would happen if a shared parameter is defined in both a shared parameter and in a family only applies to all non-system families where you can add a formula. As with anything else being transferred, I'd see the project information as overruling any in the project. Ideally, when trying to add a shared parameter controlled by a formula in a family Revit would give you a warning that the shared parameter is defined elsewhere. It would then either:
Not allow the shared parameter to be added to the key schedule while controlled by a formula
(Preferred) Have additional warning dialogue text stating "If you continue _____ parameter will be overridden" After clicking "OK" it would allow the parameter to be added and would add an asterisk to the model name or highlight the parameter field in some way, with the hoover text "this parameter is being controlled by a key schedule". If the family is edited or put in another project without that key schedule it will revert to having the shared parameter be controlled by the formula
Anonymous
11-22-201611:42 AM
11-22-201611:42 AM
This Idea is under review from 07-01-2016 08:52 PM. Why does it take so long to evaluate and make decision? ...almost 11 months !?...
Anonymous
04-09-201712:16 PM
04-09-201712:16 PM
Hi, how long are you planning to review this idea? ...
Only to give one example from a previous experience in case it helps Autodesk:
The goal was be to be able to control door Ironmongery visibility parameters on the door families (such as kick and push plate; lever, pull handle and/or push bar; euro lock, thumb turn or occupancy signage; WC and/or statutory signage, etc) through the Ironmongery Set (key) schedule, which could even be linked to an external excel file.
In the beginning it was ok to control it through door schedules but once the number of doors on the project surpassed the couple of thousands then it became a bit harder to handle it. I initially had the idea to create a few basic hardware sets inside the family with the ability to override it by instance if needed (see image), but then the number of sets started increasing rapidly and suddenly that approach was no longer enough.
I then considered creating dummy "yes/no" text parameters on the key schedule (only parameter type allowed) and then match the family parameters to them through dynamo, but it would became too messy down the road, ending up being a bigger problem than actually started with.
If we had the power to control more than "dummy" text parameters on a family through a key schedule, that would be powerful! Those specific parameters could then all be instance so to avoid conflicts, not a problem. But ideally type would override type and instance would override instance. It could work as sort of a "Global Parameters Set" with "sub-parameters" associated to it.
Or else to be able to have those "parameter sets" or key schedules inside the families to control a set of parameters at once would also be great and save huge time...
It would also be interesting if we could add a key and populate its values from within the properties panel.
Say I have window families with height and width being an instance property. If shared parameters for keyschedules would be allowed, I could preset some values in the keyschedule to have consistent window sizing.
However, when I have an off size window, I would love to have an option 'create key based on this element'. This could for example be an example in the key dropdown. That way, we could populate a key schedule based on the elements and wouldn't have to retype values in the keyschedule
I would absolutely love to be able to do this for Hardware Groups on doors. Key Lists are simply incomplete without the possibility of showing the values on plans. Either be able to Tag Project parameters or be able to use a project based Key List on a Shared Parameter.
It would avoid needing one parameter for the Key List data population and another with the same value just to be able to Tag it.
Absolutely a big wish for Revit, silly that it's not yet possible.
This issue has been around since 2006, When planning workflow and process this and calculated values in tags are stumbling blocks that require 3rd party workarounds that don't keep data live. Would be a great help.
Cannot say enough about this need for ability to add calculated values to tags. Without the need for Dynamo or Add-ins that go away. Can't vote this up enough.
Why is this not a thing? I thought surely I was simply doing something wrong. Though I'm only getting started in familiarity with shared parameters, I can't think of any reason why they can't be used in key schedules. Please, Autodesk, add this functionality.
Anonymous
06-14-201809:50 PM
06-14-201809:50 PM
So I went through this exercise I dreamed up to make it easier to create window and door schedules... only to be foiled right at the end when I couldn't find a way to schedule shared parameters in the key schedule. Turns out it's not me. It's Revit.
For a product that bills itself as a premiere BIM application it sure is lacking a lot of internal connectivity between the various sets of data that we generate. Please consider prioritising these features.
Great job on keeping positive instead of just complaining! Your post kind of changed my tone on this Monday morning. Revit makes my job a lot easier, and I appreciate that. This topic would just make Revit better and make my job even easier.
The most needed for me is to be able to create the parameters for Key Schedules from API. At this moment the Revit API is unable to create project parameters. There is a discussion about that here:
You might get it before fire tape. Fire tape is often required by many AHJ, AHCA, and is an NFPA standard and the still refuse to provide that ability.
Anonymous
11-28-201810:02 PM
11-28-201810:02 PM
Seriously. Is this not resolved yet? It's 2018. This should have been possible in 20..... like more than 15 years ago when Revit began putting the I into BIM.
I'm not looking to pay more money to have Shared Parameters in Key Schedules thanks. This should be a basic function of Revit.
Anonymous
12-05-201801:16 AM
12-05-201801:16 AM
Yup. While I appreciate that there is an ecosystem built around Revit as a platform and that there are many developers who produce some good apps that supplement Revit, I do no appreciate that Revit is missing some really basic functionality.
Keynotes? I have to edit them in a text file? Really? The list is long and tedious...
123 Search seems like a potentially powerful tool. I like the look of your work. However if I can't understand how to use it from the videos you've created (even if I can work it out) how am I meant to explain to less experience users how to create and edit the information they need in order to make Key Schedules flexible.
I'm quite sad that this is not a workable solution. Autodesk just need to 'come to the party' already!!!!!
The use of shared parameters for Schedule Keys will give us the ability to have one Pipe Type and force drop-down selection of rating of pipe type with fittings (Heavy Duty, Medium Duty, SCH 40, SCH 50) for one huge run of piping with sections of it changing with its pressure rating.
Or select from a dropdown list where these pipes are mounted for installation rates calculation on export.
The use of shared parameters for Schedule Keys will give us the ability to have one Pipe Type and force drop-down selection of rating of pipe type with fittings (Heavy Duty, Medium Duty, SCH 40, SCH 50) for one huge run of piping with sections of it changing with its pressure rating.
Or select from a dropdown list where these pipes are mounted for installation rates calculation on export.
Anonymous
01-24-201908:06 AM
01-24-201908:06 AM
2/10 of the top request have been solved and this is the 11th most voted idea. So technically it is the 9th most voted ideas that has not been implemented.
What is taking so long for a response? the programming workflow is pretty much useless without this functionality.
Yes, this will allow us to have our shared parameters in our Template were needed to act like a prepopulated dropdown list. This should have been available from the start.
Another great idea that has been under review for over 3 years. What is the point of having a Revit Ideas board if things just get put under perpetual review. Surely after 3 years some direction must be apparent. Why are we paying subscriptions when basic multi-discipline platform ideas are just ignored for years at a time.
The new Revit Public Roadmap has been posted (here) but the idea is once again not mentioned anywhere, meaning it will take a while longer for it to be implemented. When can we finally expect this idea to show up on the roadmap?
@harlan_brumm (or anyone from Autodesk) four years ago back in 2016 you told us you would provide us with an update on this issue. I feel like we have been very patient so can you let us know if Autodesk is actually doing anything with this or if your response was just a cut and paste response to make us feel like we are being listened to.
every time you need to create a key schedule you need to create new parameters as you cannot use shared parameters. this adds to the endless list of project parameters.
i dont know how this is not DEFAULT ?!?!?! aaand for multiple categories, how about? for example Wall Floors Beams together on one list. when come to concrete for example (C30/37, XC1 W0).. common parameters . i dont need 3 separate tables. this is ridiculous!
I needed it 4 years ago, I forgot about it and worked around it. My office doesnt use 2022 and I dont stalk the internet to see what the new versions have, usually they are useless updates that should have been incorporated into the program years ago
Revit is a program I use for work. Theres a lot more to life than worrying about 1 function of a computer program..... maybe someone needs to get out more