General Discussion

Sure, this is how:
8b150935-5518-4d14-b0b7-74157187fa61-image.png

Takeoff Selected: Updates the Information Takeoff table with components from the Selection Basket. You need to first add the components to the Selection Basket, for example by selecting the components from the table.

Throwing some help articles by the way:
ITO
Selection Basket

Could you specify why do you want to take off the selection basket particularly?

Hi @Matti-Kannala ,
unfortunately there are still representation problems on some ifc4.
Is it possible to have a list of ifc4 entities that are not yet supported in Solibri?
This could help us know what to model and not to model if solibri is included in our workflow.
Thank you

Thanks, @Harmen-Jorritsma and @JSN, for your valuable tips. I’ve used Excel and cleaned up unnecessary spaces, and it worked.
Thanks also to @Matti-Kannala for your offer of support.

This rule can also check this:
Rule #230 Property Rule Template with Component Filters

image.png

My update on this matter on Solibri ver.9.13.6.15

Views can now be transferred back and forth between Solibri BCF live connector and Trimble Connect BCF topics. (this is very big bug fix!) Object selection set is still not transferred on either direction, i.e. either from Solibri to Trimble Connect, or Trimble Connect to Solibri. Object Visilibility is also still not transferred on either direction.

At least issue 1 is fixed, and it makes BCF workflow workable between solibri and Trimble connect. Great thanks!

HI @majkanovic ,
thank you for your reply

Greetings,
Oussama

If you find a solution that allows both let me know. For the moment I think you have to change it every time.

@JSN @Pasi-Paasiala @manuel-furia
Seems that some Properties have this problem and other don’t
Layer, Building, Discipline, Federated Floor (and possible other) are not editable.
Application, Name (and others) are editable.
I will create a ticket for this.

i have about 400 new parameters, from what i understood from the rule 203 that we can check attributs if they exist or not but how can we check that all the parameters are integrated ?

thank you for your reply

@twosk if you can provide us with a simple example (preferably IFCs + ruleset, a .smc file works also) to duplicate the issue of intersections that should be excluded in your opinion, it’d help us to find the problem or help you in setting up your rule.

Got it working, but had to use two rows
9b5a53c1-14ad-4c05-9f25-f3b6259ef7dd-image.png

Just tested this a bit:
By using west european encoding I got “é” working in the path:

<?xml version="1.0" encoding="ISO-8859-1"?>

Check the auorun log for details:

C:\Program Files\Solibri\SOLIBRI-9.13.5\log\autorun.log

When there is UTF-8 as encoding and the file is not UTF-8 encoded then you will get this kind of error:

“org.jdom2.input.JDOMParseException: Error on line 6 of document file:/C:/Users/Downloads/autorun-test.xml: Invalid byte 2 of 3-byte UTF-8 sequence.”

@jakub-rusin said

Hope that helps at least somewhat 🙂

Haha yes at least I know how it works (or not works…) 🙂

Hi @Paul-Linder , thanks for your reply.
Is a very important topic.
Fingers crossed 🤞 for beginning of next year.

Hi,
I return to the topic to find out if improvements on the critical elements report are in the Solibri plans.
I agree with @le_branquinho.
The solution to insert result components in the selction basket is the workaround we now use… but it is not so immediate, there is also the risk that non-critical elements may end up in the selection basket. Surely the “export to excel” function would be more convenient for the user.
It would also be very helpful if there was a choice to export components in separate rows.
This makes the job easier for the BIM Specialist who then has to copy and paste the ID into the authoring software. Unfortunately, not everyone uses BCF report so the excel format is still widely used for communication.
report idea.jpg