Due to the fact that this thread is in my opinion already rather good summing up the shortcomings of the various property checking rules I will add another point here to keep the fragmentation of topics limited - but at the same time I will add another topc in the feature request section.
See here: https://society.solibri.com/topic/1902/a-flawless-property-checking-rule-with-a-full-configurable-import?_=1654094250323
The property requirements are given in tables based on the IFC Entity (+ Predefined Type) - so to keep it short, the result is that the the requirement list is differentiating elements way more precise than the Solibri component mapping does. Moreover sometimes it’s even necessary to use classifications to seperate and group elements even further (or to fix technical export issues of specific software).
So ideally we can simply use the excel import feature and load a long requirement list and check (at least categories) in a bunch.
Unfortunately this is not working out at the moment as this is not supported due to the simply fact that the column “Components” cannot be modified into e.g. a Classification name.
#9
d453a87f-4298-4c9f-892c-28d55d5ca2f0-grafik.png
#203
09b16031-205d-4559-a3d1-59bbd4196d06-grafik.png
#230
292cf8e5-9e93-4840-8c10-0ff3301df17d-grafik.png
Example: I have a list of parameters for various MEP classification categories (more than 100) and I currently see now way of importing them in just a hand full of rules without having to find out the greatest common denominator of each property first and find out the corresponding filters in laberous working steps before.
So I would have to create at least >100 rules for each category where I can load the applicable properties (0 to 20) simply because it’s not possible to change the component columns. “Any” can’t be used here because obviously not all properties have to be checked for every category. 😰
Edit: To illustrate my destiny: Instead of five rules I have to create more about 300 even when I am using the combined excel import.
3bdbaa50-4098-4f03-8ca1-e815c9d2db75-grafik.png
(I guess in the future there is also the chance to speed this up using the xml data of the csetx, but for now I am doomed …)