This is well depending on your work flow method, the idea of using instances is you can change them in the instance name info when ever you want, they update the headers, so visually they all match. Much more economical for DC reuse provided you use parent! and only need unique ones when the formula is changed.
1 Like
I did add custom variables, Attribute and Code, on both parent and child components to see how they display in Generate Reports. Seem to be fine for that. I also opened Attribute Observer and tried a couple of things. I need to practice with that because a couple of things that I expected to happen did not happen… so I must not get it.
I’ve been neglecting DC practice lately but I do need to learn a few things to make them do some things I haven’t figured out yet. Did you create “Brick” DC with mortar beds? And if so, did you create another version without the bed? I need to learn to stagger, batter and turn corners. I wouldn’t need all of that for 3D DC takeoffs but it would be nice to be able to create the detail.
Hi James,
as per forum policy, could you start a new topic, as the question and answers, techniques required are off this topic / post
Philip
1 Like
Kitchen case.skp (242.6 KB)
For an example I send one of my components. I’m sorry, but so far none of the solutions are suitable in my opinion.
make a temporary folder (“aaaa” in MyDoccoments in my case) follow the video
The proposed method of replacing components certainly gives a result, but as a workaround for the existing problem. It’s good that when the Internet is turned off, the old dialog and the method of creating a report work, in which everything works correctly. I think we can conclude that Sketchup did not work correctly in this task and either add an instance attribute to the report in the future so that there is no confusion between the Entity name and the Instance name. On this I propose to close this topic.
1 Like
This topic was automatically closed 183 days after the last reply. New replies are no longer allowed.