Revit API Fun: FamDoc.Save()/Close()/Close(true) All Need Family Full Path!

Based on our experiences in the past decades, it’s fun to play with Revit API. Here is one.

FamDoc.Save(), FamDoc.Close(), and FamDoc.Close(true) calls all need the FamDoc has a full path!

It is easy to understand for the first and third call as they will be trying to look for where the family file really resides then save changes to the file. However, the simple FamDoc.Close() also behaves so. If the opened family document is not closed, many potential issues may just occur here or there.

Close(false) seems the way to go!