Hello,
I'm trying to use a DisplayRule to filter based on element's phasing property.
The property is part of the "ObjectPhasing" property group in the definition editor, as per default Bentley NM Dataset. This same definition/property is used on a multitude of catalog items from architectural to structural and mechanical.
When creating the DisplayRule it looks like I have to select a single catalog type for each 'Condition". Isn't it possible to use some kind of wildcard?
Hello Johan,
That property has been cascaded to each of the elements. so if you see the hierarchy of the properties, the Element comes on the top and the property schemas such as Phrase, ID, etc come below to that. As those properties are not base class properties, we have to select the elements and then select the properties to get the display rules working on the elements.
I hope this helps you clarify the query,
Regards,Alifur
Answer Verified By: Johan De Cock
Yes that's how I understood it.
My question is if there is no way to get around this? It's not user friendly!
That's how the DG Schemas are structured, for now there is no way other way of doing that.
Thank you for the reply.
You write "... for now ...", are there any plans to change that behaviour?
I kind of understand why it is this way from a programmatic point of view, but I fail to see how Display Rules can ever be efficient with DataGroup data in this way. For things like "Level" and "Colour" there is already the "Elements common properties" that allow to filter across all different types of elements. Can't it be added for datagroup information?
I'll give an example from an IFC viewer (but the same workflow also works in other software, including other BIM authoring tools):
First step is to select the element type (in OBD that would be the catalog type/item). Next the property. If the first column has "all" selected then the second one gives a list of all properties that exist for any element type (not only the mutual ones). When an element type has been specified, only the properties that exist for that element type can be selected. The operator has the option "Is defined" or "Is undefined". When filtering on a certain property to be a specific value, any element that doesn't have that property defined will automatically not be selected.
Johan De Cock said:You write "... for now ...", are there any plans to change that behaviour?
That would be something for the product managers to decide.
Johan De Cock said:For things like "Level" and "Colour" there is already the "Elements common properties" that allow to filter across all different types of elements
The MS properties will show this behaviour as the MS properties are coming from an generalized schema and then it has been cascaded to the elements. For OBD, its just the opposite, We have the elements and then we have properties.
I would suggest to please file an SR so that we can have a PBI filled for this request of changing the datagroup behaviour.