Device definitions

[Conrad Preen]

@KAAC @Antti Eronen I'm starting this thread to continue discussions relating to the new device definition workflow and keep the Did You Know thread as a how-to repository. 

[Conrad Preen]

@KAAC Thank you for your specific comments! I will do my best to address them below.

 

"We have a lot of devices to build in CC and my decision for the team is whether to start working in 2025 or 2026." Use the latest version every time. Software never goes backwards.

 

"VW 2026 - removes the 'Save To Database' option". Not exactly. If we are talking about the Device Object Info Palette buttons, we have merged the functionality of the 2 buttons into 1. Since in the new scheme of things we don't have a database as such but are saving to a record attached to a symbol both buttons would logically be named Save As Symbol! So it made sense to have just one button doing both. 

 

The old text file database was a temporary measure to integrate the online community device sharing that had been part of ConnectCAD prior to the acquisition by Vectorworks.  It was far from ideal. If you wanted both nice 3D symbols and shared device data these had to be kept in sync manually. Now if you want to share a device definition with a colleague all you need to do is put a 3D symbol in a shared folder. It's a lot easier.  

 

I agree that locating the symbol+device definition in the Resource Manager for a given schematic device's make/model could be made easier. But that is more to do with the Resource Manager than ConnectCAD. Believe me we are pushing in that direction. Being deeply integrated in Vectorworks sometimes means we have to move the whole ship along with us. However, don't forget that symbols+device definitions are just rubber stamps for creating device instances. Editing the record will not change your schematic. That's by design.

 

Could Vectorworks handle workgroups better generally? For sure! There is a lot more to do there. We are working with our colleagues to improve this.

 

Vision for the future: Integrate the Device and Device Builder tools into one tool. Be able to edit device instances in the device builder dialog as a mode of this tool. Improve socket placement tools to apply same naming rules as device builder. Review all tools to ensure that sensible context-aware defaults are applied. Timeline depends on whether resources are free to develop and test.

 

"is there a plan to add the ability to create devices directly via the device builder when 'Save As Symbol 'is triggered?" No. This will be integrated into the Device tool.

 

"Are devices created in 2026 available to choose and place on the page via the device builder?" Yes. The Device Builder in 2026 looks at symbol content, not the old database.

 

"In 2026 when creating devices from a worksheet does CC look for pre-built device availability only in the pre-2026 text file device database or also in the local file for symbol devices created in 2026. Does it look in the workgroup at all for devices?". It uses exactly the same code as the Device Builder. It looks for symbols in: open documents, user folder content, workgroup folder content and application folder content. The old database file is not used any more.

 

Hope I've helped a bit. I'm aware that change can be unpopular but this was something we had to clear up.

 

Conrad

[KAAC]

Thanks @Conrad Preen - appreciate the insight, this is what I was looking for from a guidance perspective for moving forward. A couple more questions below if you could oblige.

 

If I understand the above correctly our specific workflow eventually will be...  - I understand this is still fluid and subject to change...

 

• Import a Worksheet
• Create devices from the imported worksheet
  • At this point I run a script to write physical dimensions, weight, power and some other info we bring in on the imported worksheet to the object info fields of the created devices to speed things up.
• Select a device and 'Save As Symbol' to the local file
• Choose the newly merged 'Super Device Tool' to select the saved device on the page and depending on tool mode chosen trigger the device builder to add IO's?

1 - Is the above roughly correct?

 

2 - Also with the latest update 1 for 2026 a file (ConnectCAD_DeviceDefinitions.vwx) is created in the Library/ConnectCAD/Device folder at the below path that apperad on my system to create device definitions based on what was found in  the ConnectCAD Devices DB.txt text file in the user folder ConnectCAD Database folder and these were accessible via device builder. Is this correct? 

- '/Users/UsersName/Library/Application Support/Vectorworks/2026/Libraries/ConnectCAD/Device/ConnectCAD_DeviceDefinitions.vwx'

 

3 - Finally, in 2026 a symbol and device definition is saved during the 'Save as Symbol' process. To share devices between users is it just the device definition that needs to be passed between people or do both symbol and device definition need to be shared?

 

Thanks a mil Conrad.

[Conrad Preen]

@KAAC cutting to the chase a bit... you have a bunch of device data in a worksheet and you want to create as an end result is a bunch of device definition symbols (with default graphics) in a Vectorworks document saved to a place of your choosing. Would that summarise your needs?

 

The reason I ask is because I can see such a utility being helpful in content creation generally. That kind of exists internally so we could tidy that up and release it. 

 

Regarding your questions:

 

1 - yes that sounds good

 

2- That would be created by the Migration Manager when you migrate the user folder database. Effectively it's doing the workflow I'm asking you about above. Which leads to a sneaky thought that you could add all your device data in the old database format and migrate it to create a bunch of device definition symbols.

 

3 - That's right both are created. I would always share the device definition because that gives you the 3D symbol that will be used in layout equipment items plus the device builder data. If you like to have special graphics in your schematic devices then you might share the red symbol too. It's up to you.

[KAAC]

4 hours ago, Conrad Preen said:

 

@KAAC cutting to the chase a bit... you have a bunch of device data in a worksheet and you want to create as an end result is a bunch of device definition symbols (with default graphics) in a Vectorworks document saved to a place of your choosing. Would that summarise your needs?

 

Close but not quite @Conrad Preen . We have a large catalogue of devices in D-Tools that we need to be built in VW over time. We export projects from a bill of materials in D-tools and import as a worksheet in VW. The main item missing  in 2026 is the device builder opening so as to add IO when saving a symbol. 
 

Migration manager, of course!, I was confused about how that was being done.

 

idea / Feature Request

the ability to select lines in an imported worksheet and create only devices for the lines selected.

 

Really appreciate the info, it has cleared up a lot confusion on my part…

[CharlesD]

Adding my (only slightly) related thoughts on this.

 

I am currently looking to enhance the following three items in my workflow. I believe these are common enough that it might be nice to have some default workflows setup in CC:

 

1. Make it easier to export my device definitions. Our company has external tooling/DB to manage device info. If I create a device in CC I have to manually re-create it in another piece of software. I'd love to be able to get a YAML/JSON/CSV out.
2. Make it easier to import my device defintions. This sounds like polishing up your internal tooling. But, it's the reverse of above. When I have external device definitions in a 3rd party DB, I want to bring them into CC. Ideally this is an option through a YAML/JSON/CSV. It probably wants a dialog to handle merge conflicts?
3. Make it easier to bulk modify my CC device definitions. Standards change, people disagree. What happens when a user wants to update a 1,000 device library and change every instance of 12GV to 12G-SDI? A type of interactive worksheet or script would be helpful, or it could lean on the import/export as discussed above. (I've started my own script for this, but we'll see if I get around to finishing it.)

[Conrad Preen]

@CharlesD generally I'd agree that supporting import / export is a good idea. Finding the resources to implement it all can be a bit challenging...

 

Updating large numbers of device definitions will need scripting.

 

Conrad

[Antti Eronen]

@Conrad Preen I'll try to clarify my point from the previous thread. The issue with the current device workflow is this: I'm drawing a schematic in CC and I create a new device. I click on "save as symbol" and it saves it in the resouce manager under the active document. If I want to use that symbol again in another project I have to either open the earlier document where I built the device symbol or manually move it to another location, for example workgroup folder, from the document I first made it and then move it to the my new project file. This kind of works but its quite a lot of steps for a single device and we do build a lot of device symbols in CC.

 

Am I missing something obvious or is this how the workflow now is?

Would it be possible to use a folder in workgroup folder for the "save as symbol" option and for the device builder? This would also make it possible to automatically share the device symbol with the rest of my colleagues.

 

[Nikolay Zhelyazkov]

17 hours ago, Antti Eronen said:

@Conrad Preen I'll try to clarify my point from the previous thread. The issue with the current device workflow is this: I'm drawing a schematic in CC and I create a new device. I click on "save as symbol" and it saves it in the resouce manager under the active document. If I want to use that symbol again in another project I have to either open the earlier document where I built the device symbol or manually move it to another location, for example workgroup folder, from the document I first made it and then move it to the my new project file. This kind of works but its quite a lot of steps for a single device and we do build a lot of device symbols in CC.

 

Am I missing something obvious or is this how the workflow now is?

Would it be possible to use a folder in workgroup folder for the "save as symbol" option and for the device builder? This would also make it possible to automatically share the device symbol with the rest of my colleagues.

 

You can save the created symbol in a file in the workgroup/user folder or as favorites. Then, after a resource manager refresh, you should see this in the device database.

[Antti Eronen]

What is the correct workflow on how to save device symbols to the workgroup folder? We don't seem get it working.

[Nikolay Zhelyazkov]

6 hours ago, Antti Eronen said:

What is the correct workflow on how to save device symbols to the workgroup folder? We don't seem get it working.

You should save a file with the device symbols in it in your workgroup folder\Libraries\ConnectCAD\Device\

 

Then you might have to restart Vectorworks and refresh your libraries.

 

Let me know if you have issues getting this to work.

 

Best Regards,

Nikolay Zhelyazkov

[Antti Eronen]

1 hour ago, Nikolay Zhelyazkov said:

You should save a file with the device symbols in it in your workgroup folder\Libraries\ConnectCAD\Device\

 

Then you might have to restart Vectorworks and refresh your libraries.

 

Let me know if you have issues getting this to work.

 

Best Regards,

Nikolay Zhelyazkov

So every time I need to add a CC device to the workgroup folder I have to put it in a separate file that I have to save in the workgroup folder? I'm sorry to say but this is far from a streamlined workflow. The biggest issue here is probably not how to get it to work but the whole workflow itself. Could I suggest that in future you add an option to make this automatically with the "Save as symbol" command.

[Pat Stanford]

Just put one VW file "MyDevices" (or whatever name you want). Then select the devices you want there in the Resource Manager and use the Export function and navigate to that file.

 

If you also make the file a Favorite, it may be easier to navigate to.

[EricSeipel]

You can color me stupid, and i probably go about this the complete backwards way.... but i would like to get onboard with the "official" correct way assuming it makes sense and is just as easy...

 

Currently I have an excel file with the definitions of all my devices, and add more when needed.

I export that as Tab separated as "ConnectCAD Devices DB.txt" to the Database folder.

When needed i export my job from our inventory software, paste it into a worksheet and hit Create Devices From Worksheet.

Everything gets added and i connect the lines...

It was very fast to add a new device export and create devices instantly from a worksheet.

 

Is this STUPID, SLOW, WRONG, ETC ?

What is the correct way to do this going forward?

Do i need to add every device to a drawing as an object? Save a "Library" file? How does vectorworks know to create devices from that "Library" file?

 

The old way seemed intuitive, and this new way i either haven't found enough documentation or I'm just not getting it.

[Nikolay Zhelyazkov]

9 hours ago, EricSeipel said:

You can color me stupid, and i probably go about this the complete backwards way.... but i would like to get onboard with the "official" correct way assuming it makes sense and is just as easy...

 

Currently I have an excel file with the definitions of all my devices, and add more when needed.

I export that as Tab separated as "ConnectCAD Devices DB.txt" to the Database folder.

When needed i export my job from our inventory software, paste it into a worksheet and hit Create Devices From Worksheet.

Everything gets added and i connect the lines...

It was very fast to add a new device export and create devices instantly from a worksheet.

 

Is this STUPID, SLOW, WRONG, ETC ?

What is the correct way to do this going forward?

Do i need to add every device to a drawing as an object? Save a "Library" file? How does vectorworks know to create devices from that "Library" file?

 

The old way seemed intuitive, and this new way i either haven't found enough documentation or I'm just not getting it.

- You can still do this with the cost of 1 additional step but the benefit of having automatically generated 3D symbols for your device definitions.

 

1) Do the same as before and export the excel as tab separated file

2) Store this file in the standard location as before <someFolder>\Libraries\Defaults\ConnectCAD\ConnectCAD_Database\

3) Use the migration manager to migrate the tab separated database to the new symbol based database

4) All the devices from your tab separated file will get a symbol created in a vwx file in the default content. You might have to restart VW and refresh your libraries to see this file from the resource manager

 

Let me know if this helps.

 

Best Regards,

Nikolay Zhelyazkov

[EricSeipel]

Cool Cool...

 

I don't know what you mean about (4) "created in a vwx file in the default content." I played and figured...

 

Is this a location that vectorworks inherently will now grab the symbols from when i add the from worksheet?  Yes it does

 

Where is this file located, i don't know where that "default" is? Figured that out, Resource manager, User Libraries 

 

Will a new vwx file get created every time i use the migration manager or will it just add new devices to the existing file? It updates the file

 

My only remaining question, will there be a new way to do this in the future or is it edit a text file from 2005 folder, or use device builder?

 

Thank you for taking the time to help.

Edited December 5, 2025 by EricSeipel

[Conrad Preen]

@EricSeipel We will look at creating a utility for bulk creation of device library symbols.