Get IFC parameters not working for stairs

[DGSketcher]

I can use the following to get the IFC "Name" value with all elements except stairs and handrails. The n value is returned as zero. Can anyone help explain why?

n = APPLICATION_QUERY ("ParentCustomParameters", "GetParameter(IFC.Attributes.Name)", value)

[JaseBee]

I have also noticed this, my custom id and name/tag labels don't pick up the data, just getting round to trying to figure out why now, will let you know if I can beat it.

[JaseBee]

Yep they changed it on us for the stairs, fortunately the new command works with everything else so just make it your default...

The new command is:

n = REQUEST ( "Property_Value_Of_Parent", "id", type, dim1, dim2, propertyValues)

If you want the element id then replace "id" with "Main.ID", the element id is returned in the propertyValues Parameter.

"IFC.Attributes.Name" for the name
"IFC.Attributes.Tag" for the tag

You can access all the property and classification values like this, I made a simple part to find the names that uses the command:

n = REQUEST ("Properties_Of_Parent", propertyType, parentProperties)

and spits out the values with a looping text2 command.

Like all useful requests these do not work in the parameter script.

Happy hunting.

[DGSketcher]

Thank you for the feedback JaseBee.

I ending up rewriting my label building off the code for the current "Property Label 21" using the changed REQUEST format. This also required the introduction of UI elements, which I usually avoid, to allow drilling down to the relevant IFC values.

Hopefully the rewrite is a bit more durable than the previous hacked code and seems to work with all 3D elements so far...

[Daniel Kovacs]

Hi guys,

I have looked into the issue with our developers, and this Query should absolutely work with Stairs and Railings as well! It is not working because of a bug! We probably haven't noticed this before, because (as JaseBee mentioned) we use a different method now to get these information out of elements.

Using the aforementioned Request instead is a great workaround (in most cases even a great long-term solution)! Hopefully we can fix this soon in a future update.

Kind Regards,