Let's take yet another look at element ids and maintaining connectivity with IFC GUIDs:
- Linking IFC export with modified BIM
- You cannot control the unique id
- You can control the IFC Export GUID
Richard RPThomas108 Thomas points out the important possibility to store the exported IFC GUID in an RVT BIM element parameter in order to maintain connectivity in the Revit API discussion forum threads on GUID (congratulations on the shortest thread title ever!) and asking specific GUID; is it possible?:
Question: How can I generate elements that have specific GUID?
Example - I have one or more elements and GUIDs that I want; I need to create an element having that GUID.
Answer: If you are speaking about
Element.UniqueId then the answer is no, those are generated by Revit.
This applies to both
UniqueId. These unique identifiers are auto-generated. There is NO way you could specify these yourself or assign them manually to an element.
If you are in a situation with such a requirement, there is a flaw in your workflow design and architecture.
You can probably solve it by using some other identifier. If you need to define the identifier yourself, then do so.
You cannot expect Revit or any other software to generate a GUID according to your specification.
An example of generating and storing your own GUID to identify a project that could also be used for individual BIM elements is given by the named GUID storage for project identification.
Response: We need it for IFC export. In our workflow, we have a master database from which we need to generate and re-generate objects in Revit. We would like that when exported to IFC, their GlobalId is set to something that we have generated in our own project, not newly assigned by Revit each case.
Answer: Well, sorry, you read all the unanimous answers above. You can easily program a workaround. You will not be able to force Revit to use the unique ids you need, but you can easily equip the building elements with the pre-existing ids in your own data structure and replace them in the IFC file or elsewhere along the processing pipeline. Be creative.
If you need to recreate the elements in Revit, then you need to repopulate the parameter used to store the GUID in relation to the above setting with the value you want it to be.
So, if you are creating elements in Revit from data in this external database, then just populate the parameter of that created element with what exists in your external database (removing same superseded item in Revit). Then, when exported, the IFC GUID will be generated from the parameter if the above setting is used for export.
Question: We are working on a very large project. Many engineering service providers are involved. Since Revit is not the only engineering tool people use, we need to use another software for our common data environment. This software imports IFC file formats.
We created a very detailed tagging procedure. Every element identifier will be maintained by a user. We need to keep those identifiers during IFC export from Revit. After that, we can easily link them to rest of the data that we have in Excel. But, if we lose the identifiers during IFC export, we can't do anything...
I have these questions:
- How can users create and maintain the identifiers? Can we use the parameter “Mark” as an identifier or it has to be the GUID? Can a user change the GUID?
- How can we keep the identifiers during IFC export? IFC exporting loses the parameter “Mark”, and the old GUID is automatically being replaced by a new one.
Any answer would be greatly appreciated.
Answer: The Revit IFC exporter has the option below to store each element's IFC GUID in an element parameter after export:
When the export occurs, the GUID used for the exported instance is added as an instance parameter on the instance in the Revit model:
If then the IFC is exported again later, the exporter should read this instance parameter value to use the same GUID for that export also:
Response: @RPTHOMAS108 thank you! This is what I was looking for!
Many thanks (again and again) to Richard for sharing his inexhaustible experience and providing so many great solutions!
By the way, this was also explained by The Building Coder in 2015, on accessing the IFC GUID of an imported wall.