GUID not case sensitive in Classifications
-
It is true it uses case-insensitive comparison by default. So you had it with the GUID field?
Maybe similar change to case-sensitive comparison should be done for BATID field, too.
You could argue that all of them should be case-sensitive, but I don’t think that could be done if many people rely on the current behaviour.
-
@lasse-lindqvist said in GUID not case sensitive in Classifications:
It is true it uses case-insensitive comparison by default. So you had it with the GUID field?
Maybe similar change to case-sensitive comparison should be done for BATID field, too.
You could argue that all of them should be case-sensitive, but I don’t think that could be done if many people rely on the current behaviour.
Case sensitivity can’t be added to certain items?
I solve this now by using for example GUID and Type or sometimes more parameters in the Classification rules to make sure the correct objects are Classified.
But it kind of defeats the purpose of having a GUID in Solibri I guess, since you’d want to be able to use just that instead.
-
@lasse-lindqvist said in GUID not case sensitive in Classifications:
You could argue that all of them should be case-sensitive, but I don’t think that could be done if many people rely on the current behaviour.
True, but on the other side I cannot think of a genuine use case where intenionally people really rely on this behaviour - speaking of GUID and BATID. The chance of a lower-upper case dupplciation is already rather uncommon (personally I just know it from Revit generated IFCs). However if you meant all kind of thinkable columns than I agree with you, this should not be changed.
Actually, the core of the problem is the non existent case sensitivity with IFC GUID creation in general as this could also lead to problems in other third party tools e.g. Power B. The issue in general is a bit bizarre as there is literally an entire international standard around GUIDs (https://www.itu.int/rec/T-REC-X.667-201210-I/en) - 6.5.4 basically says they should be generated as all lowercase to avoid such troubles.
-
Yes to clarify: I would change GUID and BATID comparison to be case-sensitive and leave others as they are for backwards compatibility.
-
@chris said in GUID not case sensitive in Classifications:
What ist BATID in Ifc?
BATID is BIM tool ID.
Solibri imports it from IfcElement.Tag attribute (https://standards.buildingsmart.org/IFC/DEV/IFC4_3/RC2/HTML/schema/ifcproductextension/lexical/ifcelement.htm) -
@lasse-lindqvist Good point! Thanks.
-
I have now added an internal task #8920 about starting to use case-sensitive comparison for BATID and GUID properties in classification rules.
-
@lasse-lindqvist said in GUID not case sensitive in Classifications:
I have now added an internal task #8920 about starting to use case-sensitive comparison for BATID and GUID properties in classification rules.
Great!
-
@lasse-lindqvist is this implemented yet?
-
@Paul-Linder can you check what the status is? When we check it is still not fixed!
-
@JeroenKoomen This is trivial to fix. The fix will be in the next release. Thanks for reminding.
-
Thanks @Matti-Kannala
-
We have just released beta version of Solibri 24.9 which contains this fix. If you would like to test that out before release and provide any feedback that would be great. Instructions on how to join beta program are included in the release post:
https://society.solibri.com/topic/3046/solibri-24-9-0-beta-round-open
-
M Matti marked this topic as a question on
-
M Matti has marked this topic as solved on
-
M Matti unlocked this topic on
Copyright © 2025 Solibri Inc. | Powered by NodeBB