When using the SaveAs function to save a family document with a different file extension, I found that the resulting file could still be opened in Revit. However, some features were missing:
1. The file does not display thumbnails;
2. It is impossible to load families into a project through standard methods, such as dragging files into the project or using the family loading options within the project;
3. After opening the file in Revit, it cannot be saved again as a family file with the .rfa extension;
4. Simply changing the file extension directly cannot be reversed.
Despite these limitations, the converted file remains editable and can be saved. Additionally, operations on the converted file through the Revit API are not affected.
Initially, I thought this simple conversion could be applied to an enterprise’s family library. By converting families, they could be edited directly in Revit without disrupting regular maintenance, and the enterprise could load these converted families into projects via the API. However, if the family files are transferred elsewhere, they cannot be loaded or used without certain capabilities.
After further consideration, I realized this method doesn’t require advanced technical skills. Anyone with a basic understanding of Revit development could reverse the conversion. Thus, this approach only limits the unauthorized sharing of family files. If a family has already been loaded into a project, it can still be saved as a separate file.
Still, it might serve as a simple barrier to protect families. With this in mind, I spent some time developing a program that modifies the extension of all family files within a selected folder.
GitHub: https://github.com/HuangGuaDaGuiNan/RevitCustomFamilySuffix
Must log in before commenting!
Sign Up