Looks like we have got the attribute reindexer in AC 24. Now we have a problem of limit of the number we can apply to a custom attribute index number. 32767. This is the maximum number of elements in a GDL array. Funnily enough it appears that the issue I am having applies to elements that are based around GDL.
I have been trying figure out a way to sort attributes using an index number based of a classification system number like Uniclass 2015 or MasterspecNZ. For example in MasterspecNZ Concrete 3121 so a building material of concrete in-situe would have an attribute index number 312101 so if I need to add additional surfaces or building materials then they can be added within the same number range 3121. Currently there is a limit in the number that can be used which is 32767. I need to do this because I need to make sure across a range of files that the attributes of fills, surfaces and building materials are always consistent. I need to know that the expressions for take off that I am writing will always point to the correct attribute. Failure to do so will mean inaccurate costings.
Can Graphisoft please increase the attribute index number that GDL objects can read and the part of the Archicad database that is still based on GDL can refer to so that I can plan out how I am going to manage attributes between different files.
I have a spreadsheet that has all my attributes with their index numbers listed so that if a new attribute is needed it is created specifically with a attribute number in mind. After copying elements from one file to another an audit process is undertaken to ensure that the attributes conform to the company standard by exporting each attribute list to a text file and then opening that text file in Excel. Then using an IF THEN statement the text file is checked against the company standard for compliance. This way all files are always compliant to the company standard and if a hotline is attached to a a project file, like a standard kitchen, bathroom or laundry we know that the attributes will always align.
I don't think the attribute index is the problem here, particularly when it is a numeric only value. If I had 32k element attributes I doubt I could find what I was looking for quickly. A better request would be to ensure there is access to an alphanumeric code field for flexible entries like "J-40-100" and a separate description field for all attributes. However, AC is currently not rigged that way and everything is merged into the description including the code; layer names being a good example. AC is pretty good in the GDL department at managing and breaking up strings, if you need to interrogate the index.
Apple iMac macOS Big Sur / AC24UKI (most recent builds)