Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
you can rename this within a family using the API 😉 but even this is a painfully process of swapping the parameter to a family parameter, deleting the share, and recreating a the shared parameter with new name.
The point is to rename for classification sake. Let's say we update and maintan a shared parameters files since 2009, but for a reasons, years later we want to group and rename them for consistency...
the point is: without additional software the shared parameter management is horrible in general. A shared parameter name should be able to be renamed whenever I want, because it is the GUID that identifies the parameter. In addition a shared parameter should have several optional additional names, depending on the language settings of the user. If you work on international projects or you create families for many countries, this is so much pain.
A shared parameter is by definition "univocal" having a unique ID: it is at the base of the functioning of the "shared parameters". Changing the parameter name without changing the ID will cause errors between objects, especially with loaded families. What you ask is already there: new parameter and then cancellation of the old one.
yes i agree with you but when you have 10eme of parameters to modify it is a long task, without interest and sources of errors. There are many things I would like to do and do not do because of this
Yes indeed there are several solutions but it is necessary, again, to pay in addition whereas the suites of software AEC costs a certain price. Moreover for these pluggins, maintenance and support are not necessarily effective, often in English and not completely adapt to the needs. When you deploy BIM processes the financing of its tools, in addition to the price of the licenses of our modeling tools, is always to justify to the management who do not necessarily understand the necessity, finally I have not badly not this chance. It would be interesting that Autodesk decide to do what is necessary because I do not find it normal that users "tinkering" with multiple free or paid solutions like Dynamo.
Since Revit internally only cares about the GUID and quite happily handles different names for the same shared parameter in different families this idea makes good sense, especially for internationalisation.
If you create two shared parameters, let's call them height and width, save the shared parameter file, start a family and use those two parameters. Now close all the files, open the shared parameter file and edit it in notepad, change the names of those parameters to largeur and hauteur respectively, save the file with a new name (perhaps suffix with -fr). Create a new family use the french parameters. Now start a new project, first bring in the french family, check the parameters - they will have the french names. Now bring in the first family, check the parameters, voila! they will also have french names.
Thank you @MichaelWarwick7522 I know that there are several solutions to manage the shared parameters but the manipulations that you describe are not within the reach of a novice. When you have to rename tens of parameters in your models, your families, your labels, do it during the project, ... after 2 hours your eyes scratch you. Some plugins exist and do it !! So why not integrate the basic software! It's still a key element in Revit.
for example, if they allow us to add two additional names (on one the same parameter), with the possibility to change priority order between alias and to rename the one of with lowest, we will be able to:
- change (alias)names
- modify according specific BIM protocol, the link with office standards can be kept
- avoid errors, when Revit detects an error he will be able to try an alias of lower order.
- aliases should always be unique, during loading a family in project, and when some aliases are already in use, Revit can prompt a message and give a brief comparison, recommends to rename, asks which aliases to keep
- alias with highest priority will be automatic pushed in the loadable family’s on highest priority level, other existing alias have move to lower order
- formulas should use Autocompleet and show only the alias with highest priority (others shown with rollover)
does it have trial period? to my understanding, in order to rename existing SPs in RVT, you have to first DELETE project parameters which are SPs, then upload all RFAs w/ renamed SPs, is it correct?
Michael Warwick:
do you mean both French and English names using same GUID, or basically ONE single same SP?
