Search for a command to run...
Series
Undocumented findings, verified procedures, and working code for the Revit API and the broader Autodesk ecosystem. Everything here was measured before it was written.
A workaround for the long-standing FamilyManager.GetDescription gap, using the undocumented ParameterUtils.GetParameterSchema and the Forge parameter schema. Environment Revit 2025 · RevitAPI.dll 25
Autodesk's help says shared parameters cannot be renamed. That is true of the direct operations and false as a general statement. There are two routes: migrate to a new GUID, or rename while keeping t
The procedure this post used to describe traverses the family tree leaf-to-root and reports success. It does not do the work: parameters that live only in nested families never get their description,
ParameterUtils.DownloadParameter is documented as a cloud operation. It is not. Register your own schema server and it works entirely offline, in project documents, and, as it turns out, in family doc
Measured end to end on a control project: the rename preserves GUID, ElementId, group, instance condition and value. Tags need no intervention. View filters need no intervention. Schedule fields keep
Which parameters does a label in a tag family display? The question has been open on the Revit API forum since 2015, under an internal wishlist item that reads "API access to read and write labels". R
