Nikolay Zhelyazkov

- Subparts are special parts of complex objects. Examples for subparts are wall components, cable sections, bridle legs, etc. There is no easy way to see what is defined as subpart and what not. I find it easy to create a database worksheet, list all objects, click on Include subparts and then show the part type name to see what subparts are available in the file. The idea of subparts is that they are not just graphics in the complex objects but they come with some important data too. - Walls and slabs are not defined as plug-in objects and that is why this option does not work for them... - I think that there are 2 ways to match a subpart to a criteria a) The parent matches the criteria and include subparts automatically adds the subparts in - for example "Object is Wall + include subparts" - gives you all walls and their components b) You make the criteria about subparts and then only the subparts that match it get included - for example "Subpart type is Component + include subparts" - gives you all Component subparts of walls, slabs and anything else that has these

You can export resources to other files using Right Click -> export. The TBB Styles are resources too so you can do the same with them. Or you can open your library file and then import the resources there.

- Here is the help on the criteria dialog with all of the options explained - https://app-help.vectorworks.net/2026/eng/VW2026_Guide/Worksheets/The_Criteria_dialog_box.htm?rhsearch=subparts&rhhlterm=subparts subpart

I can only say that this is on top of our list with things to improve in the data tag. 🙂

- Thanks for the test file - Thanks for taking a look at this. From your explanation it sounds like a bug to me. I will log it in our database and we will work on a solution.

- Yes, this is currently not possible with the rack frame. I will add this as a wishlist item in our database. Thanks for reporting!

Hello @barnaby, Can you please share a sample test file showing the issue? Best Regards, Nikolay Zhelyazkov

Hello all, I am not that familiar with data viz but it looks like it has troubles with subparts/components. Having this logged as a bug is the way to go so that the responsible team can look into it. Best Regards, Nikolay Zhelyazkov

Hello @ChrisWelsh, In ConnectCAD Settings there are options to offset the circuit texts which you can try. As for the socket, selecting different text style symbols in the socket OIP can also help. Best Regards, Nikolay Zhelyazkov

Hello @Ragnell, The display column in the Manage Sheet/Project Data dialogs is editable only for unstyled title blocks or when editing the TBB style. Could it be that your title blocks are styled? Then, you should edit the style and make the changes from there. If this is not the case, can you share a sample file showing the issue? Thanks, Nikolay Zhelyazkov

This seems to be a bug related to the crop of the viewport. If I make the crop bigger to see the whole roof the data tag is able to tag it. We will look into this, thanks for reporting!

Hello @Tom W., @Sbd, Can any of you share a file where the data tag does not see the roof components so that we can check what is going on? About tags looking inside symbols, currently nothing has changed about this. - We are actively researching this and it is on top of our list with data tag improvements to do.

Hello @Matt Strong, The fix for this is in 2026 U3 which was recently released. Best Regards, Nikolay Zhelyazkov

@jbronson1206 from what I see your worksheet database row is set to list all objects in a specific layer. The default Current Layer Circuit Report is set to list all circuits in a specific layer, so maybe you modified the database criteria in your file? If you edit the criteria and set it to look for Circuits only you will get rid of most of the N/As, because they come from non circuit objects from which you try to read circuit data. This will also make your worksheet smaller and faster, as the extra rows from the extra objects will be removed. Let me know if this helps.

Hello @aheininen, I will make an enhancement about this in our database so that it can be considered. Best Regards, Nikolay Zhelyazkov