The interface between Dlubal and Revit works internally with so-called Global Unique Identifiers (GUIDs). Revit assigns a GUID to each object. During the import and export, this GUID is transferred via the interface and added to the corresponding Dlubal object (member, surface, etc.).
By using GUIDs, you can carry out updates in both directions with only those objects needing to be updated that are affected by changes. Other objects remain unaffected. This results in a better compatibility during the data exchange.
TIP
Due to the GUID assignment, we do not recommend the Undo function: Since GUIDs are only assigned by Revit, they are also exchanged when you export from RFEM/RSTAB to Revit. In this way, objects that have been modified or newly created in RFEM/RSTAB receive new GUIDs in Revit. They will be yet returned to the RFEM/RSTAB during the export to Revit. If the Undo function is used in RFEM/RSTAB subsequently, the GUID updates are undone, too. When exporting to Revit again, the objects can no longer be matched with the GUIDs (old GUID in RFEM versus new GUID in Revit). Thus, “duplicate” objects are created in Revit.
The comparison requires that each object in Revit has a corresponding counterpart in the Dlubal application. For example, Revit treats each line support individually. If a line support type is assigned to several lines in RFEM, duplicates of the line support type are created when exporting to Revit. A line is assigned to each duplicate. Subsequently, a one to one comparison is possible.
TIP
Due to the described functionality of the interface with the resulting modification of the Dlubal model data, it cannot be ruled out that the results will be deleted. Therefore, it is recommended to export the model to Revit before the calculation is made. The results can be transferred retroactively in a second export process.