203 - Value conditions?

JSN

What’s the point with “Optional” and “Must not exist”? How should those options be used to get valid issues?

I mean, I get an error description but it does not really make sense to me.

Matti

The Optional is for checking property values that are optional, but if they exists they have some requirements.

The Must not exist is not often needed. It can be used to check NULL value of a property. E.g. could be used as gatekeeper rule to find the one with NULL.

From the https://help.solibri.com/hc/en-us/articles/1500004738242-203-Required-Property-Sets

Value Exists: Select the value from the following options:

Optional: The property can have a value, but it is not required.

Must exist: The property must have a value.

Must not exist: The property must not have a value.

JSN

@Matti-Kannala

Thx for clarification, that’s basically what I thought but what is if there is no such Property in the model at all? I still getting an error - on IfcBuilding due to the behaviour of 203 - which is not understandable as it is flagged as optional …

https://imgur.com/a/dqVVjHw
(Idk why but can’t upload images here currently, I always get a parsing error)

john.lipp

@JSN

Optional should probably read: “The required property must exist and can have a value, but that value is not required”

It sounds like you want to check for blank TypeOfBrick properties and have a result only if a component has a TypeOfBrick property, with no value.

In the checked components filter, if you include walls with that property defined, it will ignore the ones with the missing property set/property. (You could also use a filter row to exclude walls that have that property Undefined)

There seems to be something wrong with the image uploading, so I’ll have to textually put the filters that should work.

Checked Components:

State: Include
Component: Wall
Property: Pset_WallSpecific.TypeOfBrick
Operator: Is Defined

Property Sets:
Component: Wall
Property Set: Pset_WallSpecific
Property: TypeOfBrick
Value Exists: Must Exist
Value Conditions: X=*

JSN

@john-lipp said in 203 - Value conditions?:

In the checked components filter, if you include walls with that property defined, it will ignore the ones with the missing property set/property. (You could also use a filter row to exclude walls that have that property Undefined)

Of course John, I am aware of that, it’s, as you noticed. more the point that description and expection is diverging. Or in other words, imagine you have a list of properties you want do check and you use the excel import tens by tens of times cause you want to work smart as the amount of properties and rules is already an advanced number … but then you would have to adjust the filters anyhow as e.g. optional is not supposed to be working as expected.

https://imgur.com/a/8qHRDEk

It’s just another point to add on the extended list of what’s wrong with the property checking …
https://society.solibri.com/topic/1902/a-flawless-property-checking-rule-with-a-full-configurable-import?_=1656313890733

BIM1337

Old topic here but when doing a value for must not exist.
Checked Components:

State: Include
Component: Wall
Property: Pset_WallSpecific.TypeOfBrick
Operator: Is Defined

Property Sets:
Component: Wall
Property Set: Pset_WallSpecific
Property: TypeOfBrick
Value Exists: Must not Exist
Value Conditions: X=Dummy

It says all values can’t exist instead of only the values that have IfcText “Dummy”.