
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi all,
in the early days I thought that ElementId was a stable way of finding elements in a document, then I learned that UniqueId was the proper way.
But I havent been able to find enough coherent information about it to really understand it and I've been reading lately that we should use the uniqueId as a identifier in multifile projects (multiple centralfiles), because its only guaranteed to be unique in one centralfile.
This is what I've learned so far (From Jeremy Tammiks Blog among others):
The UniqueId 40 characters long and is made up from 2 parts, the first is internally called the EpisodeId and the second is the hexadecimal representation of the elementId. I've read that people complain about the fact that two revit files from the same template will have the same UniqueIds for the elements that are created in the template. So I guess that the EpisodeId cannot be used as a "file guid".
However, its stated by Arnost Lobel that the UniqueIds purpose (one of many?) is to have a stable way of identifying elements in a workshared environment, because the elementId of an element can change.
OK, then, but if the last part of the uniqueid is the elementid in hexadecimal form, wont that change the uniqueid also?
I've also found in a forum post that first part is connected to the WorksetId.
With all this in mind, is the best way of identifying elemtents in a multifile to create a guid for each element and store it to them using a locked and hidden parameter (or extensible storage)?
Thanks for any help figuring this out!
/Erik
Solved! Go to Solution.