Hi,
the approach from Christophe is I think the best for your use-case. I would personally do it exactly like this.
Create user attributes, one per each part of your unique name. The attributes for non-topology-related parts:
- FamilyEquipmentCode
- ObjectSpecializationCode
- OrderNumber
Assign these attributes directly to your PythonPart in the script.
Assign the building code to the building itself in the building structure (right-click on the story: assign attributes). See attached image. Do the same with the story number.
Then define a formula attribute (In my example on the screen shot it is the ElementCode), that incorporates all the information you need into one string. E.g. like this:
TOPOLOGY("Building";@BuildingCode@)+"|"+TOPOLOGY("Story";@StoreyNumber@)+"|"+@Code text@
You can also assign it on your PythonPart in the script, just without providing a value, because it will be calculated by Allplan.
Alternatively: instead of accessing the attributes of site/building/story you with
TOPOLOGY(...) (which is possible only in Allplan 2024) you can access their
name with @586@, @451@, @452@ respectively. See ...\prg\AttributeManager.exe what numbers you must access. Search for attributes with the name beginning with "Topology_..."
I am aware, that the information about the building code and the story number are not taken from the floor manager as you planned to do that, but from the building structure. This is however better place for this kind of information