When dRofus exchanges data with Revit Project Parameters (, as configured in the Active Configuration) Attribute Configurations, it will allocate data using the name of the Project Parameter only. If the Project Parameter does not exist in Revit then it will be automatically created as a Shared Project Parameter and populated by dRofus.
Note that Shared Parameters that are automatically written by dRofus to a Shared Parameter text file will be placed into one of two Shared Parameter Groups. The exact names of these Groups is important for dRofus to be able to locate Shared Project Parameters:
"drofus instance parameters"
"drofus type parameters"
The concept of Shared Parameters in Revit means they are defined via an external Shared Parameter File which allocates each Shared Parameter a unique Global Unique ID. This Global ID ensures that Shared Parameters across several Projects can be coordinated and Unique.
For larger groups of Users working together on the same project, it is very important to understand the implications of this.
It is
...
recommended that one Project Administrator User takes control of the Shared Parameters File, creates and correctly names the applicable Parameters in advance,
...
and shares this file as a read-only file with other Users working on the same Project.
GUID’s stored in dRofus
To prevent projects without a shared parameter file to have duplicate properties when syncing with dRofus, dRofus will store shared parameter GUID’s when Revit properties are created in Revit during sync. All other users that are logged into the same database and uses the same Attribute configuration, if those attributes don't exit locally, shared parameters will be created in Revit with the GUID’s stored in dRofus. The result will be that all users will have shared parameters with the same parameter GUID’s.
For existing attribute configurations with shared parameters (where GUID’s not yet is stored in dRofus), an BIM Admin user, without the parameters locally, runs sync and shared parameters are created for her and those GUID’s will be saved in dRofus.
The default attribute configurations and default dRofus parameters. like “occurrence_id have predefined GUID’s. this means the same “occurrence_id” for all projects and customers if they use default dRofus parameters.
If you copy an attribute configuration, shared parameters GUID’s will also be copied (in dRofus)