Add Object Parameter to Label

[Lewis at Flourish]

Hi there, 

I have two questions -

Q1 is about technical skills in AC. E.g "how do I do 'Thing X' in AC?"

Q2 is about documentation philosophy. E.g. "is doing 'Thing X' an appropriate way to approach the problem in light of how AC is intended to be used?"  

Q1: Technical Skill 

is it possible to edit the parameters of a label to be able to read any chosen parameter within an object?

For example - in the screenshot below, the mixer tap has a 'product code' parameter which I would like to be able to label on drawings. 

I have inspected the parameters of the 'Classifications & Properties Label' but need direction on how to amend the script to display the parameters of the object in screenshot 1.   

Q1 - Philosophy

To my mind, labelling an object based on a parameter that is 'baked' into the object leaves much less room for contradictions between your model and your schedule. For example, I love the Skin List label because it can report on BMAT IDs, and if I change the BMAT ID of a certain material, the text in all the labels will update automatically.

I come from Revit-land, and I struggle with the idea that there isn't a way (for example) to change 'Mixer Type 1' to 'Mixer Type 2' and for the label to automatically change from the predefined code associated with Mixer 1, to the predefined code associated with Mixer 2.

This might not be a big deal on small jobs, but labelling contradictions creep-in on big jobs when (for example) a handful of mixers are being changed to a different product selection, but the code does not update with it.  

Operating system used: Windows 3001.3000

[Lingwisyer]

Hm... At a quick glance, the Caroma Specify website seems to have had an update and the library now shows individual products in other formats rather than the consolidated libraries... The libraries contained multi-objects, some of which are no longer part of the catelogue, so I assume they removed them due to being outdated. Hopefully they release updated AC libraries at somepoint, maybe containing individual objects for easier updating.

[Aaron Bourgoin]

Thanks for your comment. As always.

[Patrick M]

sorry, did not read the full thread, but this should all be done through properties now. Any info attached to an objects parameter list is a dead end in so many ways. 
Properties are an open door for annotation, scheduling, and sharing info