Applying updated templates to old documents

[laukejas]

I have completely reworked my templates for parts, documents and drawings, and I still have like 5 ongoing projects with ~400 documents in total that were created with the old templates. I am looking for a way to retroactively apply the changes I made in the new template to these old documents.

Changes I made are:
Document Properties (lots of stuff, several dozen changes)
Hide/Show Types (visibility of sketch relations, dimension names, etc.)
Annotation visibility
Turned off "suppress features" in default configuration in parts and "suppress new components" in assemblies
Selected "Configuration name" in default configuration (BOM Options)
Tree Display -> Show Component Name and Description in assemblies
Adjusted scene parameters
Added Bounding Box
Added several default Custom Properties

I found this tool to copy Document Properties from one document to another, but as you can see from my list, Document Properties are just a small part of the changes I made.

I think most of these changes should be doable with API (macro), but unfortunately macro recorder doesn't capture most of these changes, so writing it manually would be a lot of work.

I think it would be simpler if I could just re-create these documents from the new templates, and then copy over the content (Feature Manager Tree) from the old documents. This is actually very simple with assemblies - just create a new assembly from the old one, and then dissolve the old one. But with parts, I don't see an easy way - simple CTRL+C only works for simple features, not entire model history. Or maybe there is some way? As for drawings, I only have a few, so I can re-create them manually.

A few things that might make this easier if going by this second approach - I don't need to transfer material, since I reworked my material library anyway and will need to re-apply new materials. Same for Custom Properties, it would be easier to re-write them than try and convert old ones.

I am sure this is a common issue, but I haven't been able to find much useful info aside from that old tool. Can anyone share any tips and tricks to make this transition easier?

[SPerman]

#task from Central Innovations can automate most of what you are asking for. It has built in features for some of it. It will also run a custom macro (or several) along all selected parts.

@mp3-250 has done quite a bit of research documenting and understanding the document properties. He talks about it in this thread, but there might be another with more info: System option and document properties

Depending on the age of your files, they would still be based on "old templates". I think the old templates fear an old wives tale from DSS, with little evidence of problems in recent years, but I could be wrong. If you truly want everything on a new template, the only way to do that is your second method. If you want to keep the model history, and all of the relations, that would be quite a daunting task. It would certainly require more coding effort than making changes to properties.

[laukejas]

#task from Central Innovations can automate most of what you are asking for. It has built in features for some of it. It will also run a custom macro (or several) along all selected parts.

@mp3-250 has done quite a bit of research documenting and understanding the document properties. He talks about it in this thread, but there might be another with more info: System option and document properties

Depending on the age of your files, they would still be based on "old templates". I think the old templates fear an old wives tale from DSS, with little evidence of problems in recent years, but I could be wrong. If you truly want everything on a new template, the only way to do that is your second method. If you want to keep the model history, and all of the relations, that would be quite a daunting task. It would certainly require more coding effort than making changes to properties.

Thank you, I wasn't aware #task can do this. Definitely worth looking into.

But yeah, some of my parts were based on templates that were originally created back in 2002 or so, and updated over the years. I do occasionally have problems with them (mostly when doing sheet metal and weldments), so it might make sense to re-create templates entirely from scratch. But that leaves me with only option #2. I know I could do Insert Part of the old doc into a new doc from new template, but that makes modifications much more difficult. Exporting into Parasolid, reimporting, and recreating features with FeatureWorks also won't work, my parts are too complex and have configurations. Can't think of anything else.

But maybe there is some way to transfer all features from one part to another? I wonder if anyone has made some tool that automates this?

[gupta9665]

Have you tried insert part into part, and then breaking the link?

[laukejas]

Have you tried insert part into part, and then breaking the link?

Break how?

You mean External References -> Break All? Or selecting "Break Link" when creating Insert Part feature? Neither of these imports sketches and features...

EDIT: correction, it does work for some parts (not all of them, not sure why), and for some it just explicitly shows error message, like this:

And even when it works, it also deletes all equations...

[gupta9665]

Sorry, but I do not think there is any other alternative. There might be some paid tools available but there won't be any less costly version.

[Ömür Tokman]

would you look into this?
I am adding the macro. I remember it as bulk anted changing.

set language from subtitle options.

[laukejas]

would you look into this?
I am adding the macro. I remember it as bulk anted changing.

set language from subtitle options.

Thank you, this looks like a great tool to update drawings. I'm saving it for later. But for now, it's far more important for me to transfer parts to a new template. But perhaps like Gupta said, it is impossible after all...

[AlexB]

I don't think it's necessarily impossible, but it may need to be tailored to your situation (as Deepak (@gupta9665) mentioned).

The problems for me when I've run into this are with BOM tables and revision tables. It's difficult to update the formats of those if they've changed without just re-adding them. Then you have to deal with placing balloons again and re-attaching leaders, etc. So, it's possible, but knowing exactly what you're going from to what you're going to helps in developing a solution to update the sheet templates.

Then if you're using blocks on your template, you'll run into determining which instances need to be removed unless you get rid of them all and re-add them again. It's a whole convoluted process.

You may find a generalized solution that can get you most of the way there but I doubt there's something that will work right out of the box to do what you need.

[laukejas]

I don't think it's necessarily impossible, but it may need to be tailored to your situation (as Deepak (@gupta9665) mentioned).

The problems for me when I've run into this are with BOM tables and revision tables. It's difficult to update the formats of those if they've changed without just re-adding them. Then you have to deal with placing balloons again and re-attaching leaders, etc. So, it's possible, but knowing exactly what you're going from to what you're going to helps in developing a solution to update the sheet templates.

Then if you're using blocks on your template, you'll run into determining which instances need to be removed unless you get rid of them all and re-add them again. It's a whole convoluted process.

You may find a generalized solution that can get you most of the way there but I doubt there's something that will work right out of the box to do what you need.

But you're talking about drawings here, right? I don't need to transfer these to a new template. I just need to do this with parts and assemblies. Mostly parts, transferring model history (sketches, features, configurations, equations, etc.). Everything else is simple enough to fix manually, but this bit is what takes most time to re-make.

[AlexB]

But you're talking about drawings here, right? I don't need to transfer these to a new template. I just need to do this with parts and assemblies. Mostly parts, transferring model history (sketches, features, configurations, equations, etc.). Everything else is simple enough to fix manually, but this bit is what takes most time to re-make.

Yes, I was referring mostly to drawings, but a good amount applies to part and assembly models to. As you mentioned, you have a lot of customized configuration property options selected, display options, etc. so a general tool will only get you part of the way there.

This does give me an idea for a new tool/utility that could be useful for the masses.

[laukejas]

Yes, I was referring mostly to drawings, but a good amount applies to part and assembly models to. As you mentioned, you have a lot of customized configuration property options selected, display options, etc. so a general tool will only get you part of the way there.

This does give me an idea for a new tool/utility that could be useful for the masses.

Yeah, while were discussing this, I wrote a macro that can update a part made with an old template, to match the settings of a new template. That is easy enough. Problem is transferring all the part info into a fresh part made from a new template. Parts made on old templates often give lots of issues, no matter how much you update them...

[imaca101]

#task from Central Innovations can automate most of what you are asking for. It has built in features for some of it. It will also run a custom macro (or several) along all selected parts.

@mp3-250 has done quite a bit of research documenting and understanding the document properties. He talks about it in this thread, but there might be another with more info: System option and document properties

Depending on the age of your files, they would still be based on "old templates". I think the old templates fear an old wives tale from DSS, with little evidence of problems in recent years, but I could be wrong. If you truly want everything on a new template, the only way to do that is your second method. If you want to keep the model history, and all of the relations, that would be quite a daunting task. It would certainly require more coding effort than making changes to properties.

The opposite is true, DS hid the problem for years - we only found out after reporting major bugs (caused by old version templates), at which point our VAR confessed all.

[Glenn Schroeder]

If all else fails with Drawings, you can always start a new Drawing with your new template, then copy and paste sheets from the old drawing to the new one. Any annotations that haven't been overridden with the Layer or Line Format tools will use the new Document Properties.

[mp3-250]

The opposite is true, DS hid the problem for years - we only found out after reporting major bugs (caused by old version templates), at which point our VAR confessed all.

In the end DS made the VARs say to us:

"Hey you did not know you needed to remake ALL your templates at every SW version update? LOL"

with a straight face.


The little problems we are facing:
- there is no tool to compare two templates
- file properties are not exportable for about 50% of the options, there are about 1700 settings (including fonts settings etc) inside a file property
- you cannot swap an old template without breaking half of your models
- some option in file properties just does not stick and reverts to some random default (section arrows, aux view iirc)
- SW administrative tools are a (bad) joke, bug ridden and not working as expected (also breaking good data)
- SW 98 (beta) template was still floating around somewhere back when we updated at SW 2022 (and it was breaking a lot of stuff) hope they get rid of it...

etc etc

[AlexLachance]

In the end DS made the VARs say to us:

"Hey you did not know you needed to remake ALL your templates at every SW version update? LOL"

with a straight face.


The little problems we are facing:
- there is no tool to compare two templates
- file properties are not exportable for about 50% of the options, there are about 1700 settings (including fonts settings etc) inside a file property
- you cannot swap an old template without breaking half of your models
- some option in file properties just does not stick and reverts to some random default (section arrows, aux view iirc)
- SW administrative tools are a (bad) joke, bug ridden and not working as expected (also breaking good data)
- SW 98 (beta) template was still floating around somewhere back when we updated at SW 2022 (and it was breaking a lot of stuff) hope they get rid of it...

etc etc

People from Dassault have told me straight-up that templates shouldn't be an issue and a VAR saying that the template is an issue is generally a VAR that does not want to do the work to find out what setting in the template is causing the specific issue. If your VAR reports back with a "it's your template", get a second opinion from another VAR. That is what I was told by many people including one who works for a VAR when I went to visit them. John Sweeney confirmed it to me, they also built a document to explain how to "update" old templates. Here's the preliminary version of the document they were building, John told me the completed version is pretty much the same.

[DennisD]

People from Dassault have told me straight-up that templates shouldn't be an issue and a VAR saying that the template is an issue is generally a VAR that does not want to do the work to find out what setting in the template is causing the specific issue. If your VAR reports back with a "it's your template", get a second opinion from another VAR. That is what I was told by many people including one who works for a VAR when I went to visit them.

@AlexLachance, I have also talked to several at SWX (not corporate DSS, but ones in charge of the real CAD software) and they said the same thing. Templates are not the issue that people make them out to be. Sure, it is a good practice to recreate templates, but not a source of all troubles.

It's a strawman argument to point to the templates as a source of all problems. So is saying "You don't have a certified video card. I can't help you until you get one." Any VAR that uses this as an excuse to ignore your problems is lazy, inept, or worse. They should help you. Period.

If the templates were such an issue SWX (not DSS) would issue a tool that allows you to create new ones based on the old ones, or to convert/update an "old" template to a new one. BTW, has anyone bothered to write a macro to do this?

[mp3-250]

@AlexLachance @DennisD

We had all strange things happening with SW, our template was made with SW 2012 and not updated only until SW 2022 update, 10 years later. SW had at least 3 major updates of incompatible feature in the meanwhile.
We had weldments bodies changing material on their own upon rebuild and Cutlists going crazy, properties still linking the old file after creating a new file in pdm, all sort of oddities.
I remade the templates from zero for 2022 and 2023. In 2023 DS introduced the transparency in drawings a new setting not present in the old templates: it was bugged and needed an hotfix to be recognized by SW.


DS says:

Question
Is there an official confirmation that working with updated document templates is a recommendation?

Answer
The SOLIDWORKS® Research & Development team suggests that all templates are forward compatible. Therefore, if there is a problem, it can indicate a defect that requires evaluation.
Keywords S-075055,1-8FZR5CW

But I can say the above statement is utterly FALSE.
When I firstly tried to make a new template I created by accident a new part file based on SOLIDWORKS 98 BETA that for some reason was still floating around inside SW 2022.
Surprise: the sensors were completely broken by it. They probably forgot to say "forward compatible" at what percentage?



QA00000332458 The final version of whta Alex posted apparently

Question
Does SOLIDWORKS® software require new template files each time I upgrade SOLIDWORKS® software to a new major version?

Answer
SOLIDWORKS® software is continually improving. Sometimes these improvements are fundamental, for example improvements regarding how features operate or save data.

To use changes introduced in each major release, SOLIDWORKS User Success recommends that you resave your templates. When you resave your templates, they update to the latest version.

In addition, if your template files contain Cosmetic Threads or Sheet Metal Features, then consider the following recommendations:

Cosmetic Threads
SOLIDWORKS® 2019 improved the quality and performance of Cosmetic Threads.

Key Takeaways:

Resaving a file does not update any existing pre-SOLIDWORKS 2019 Cosmetic Threads.
New parts created with new templates use the new Cosmetic Thread architecture.
New parts created with legacy templates (those containing Cosmetic Thread features created before SOLIDWORKS® 2019)
Do not use the new architecture.
Do not use the performance or quality improvements.
You can upgrade these legacy template files and legacy part documents to the new architecture using the Upgrade Cosmetic Threads command (see the following recommendation).

Details:
For more details, see the 2019 What’s New document or the Upgrading Legacy Cosmetic Threads topic in the help content.

Recommendation:
Select Tools > Options > System Options > General > Allow cosmetic threads for upgrade.
Open your template, right-click the top item in the FeatureManager Design Tree and select Upgrade Cosmetic Threads. This menu item does not appear after you update the cosmetic threads.
Save the template. Files based on these updated templates use the new architecture to improve the quality and performance of Cosmetic Threads.



Sheet Metal
Changes made in SOLIDWORKS® 2013 improved the quality, performance, and fundamental behavior of Sheet Metal.

Key Takeaways:

It is impossible to update Sheet Metal features from SOLIDWORKS® 2012 or earlier.
Template files and part files from SOLIDWORKS® 2012 or earlier keep the original sheet metal behavior.
Saving a part file to the new version does not automatically upgrade the legacy Sheet Metal features. However, template files are slightly different:

1. Legacy templates with NO existing Sheet Metal features:

SOLIDWORKS® 2014 and later apply the new Sheet Metal architecture automatically to new parts created from legacy templates that do not contain any existing Sheet Metal features. When you create parts from these legacy templates, SOLIDWORKS software in addition applies the following improvements:

Quality
Performance
Functional

2. Legacy templates WITH pre-existing Sheet Metal features:

SOLIDWORKS software does not apply the new architecture improvements to these newly created parts if:

You create parts using legacy templates
The legacy templates contain existing Sheet Metal features created before SOLIDWORKS® 2013

You create parts using legacy templatesThe legacy templates contain existing Sheet Metal features created before SOLIDWORKS® 2013

Details:
For more details, see the 2013 What’s New document or the Examination of the FeatureManager Design Tree topic in the help content.

Recommendation:
Verify if Sheet Metal features from earlier than 2013 exist in your template files. New Sheet Metal features that you created in part files based on these templates use the new architecture if you:

Do not locate these Sheet Metal features from earlier than 2013 in your template files.
Use SOLIDWORKS® 2014 or later.

Consider saving the templates in the latest version of SOLIDWORKS®.
Keywords

The one below has another small caveat (bold mine):

Question
In SOLIDWORKS® CAD software, how do I replace an old template with a new version?

Answer
This solution describes the best way to update a template with the current version of the SOLIDWORKS® CAD software.

The fastest way to update a template is to use an existing template create an empty part, drawing or assembly, and then save the part in the ‘Part Templates (*.prtdot)’ format. However, this is not the best or most accurate approach because the save retains the original (old version) structure and does not fully convert the main structure. The presence of old data can influence negative behaviors in Sheet Metal, Cut List and other functionalities.

As a best practice, use the following approach to update a template:

1. Close the SOLIDWORKS application.
2. Rename the folder at ‘C:\ProgramData\SOLIDWORKS\SOLIDWORKS 20XX\templates’ or rename the folder specified in Tools - Options - System Options - File Locations - Document Templates'.
3. Create a new folder at ‘C:\ProgramData\SOLIDWORKS\SOLIDWORKS 20XX\templates’ or specify a custom path.
4. Open the SOLIDWORKS application.
5. Go to Tools - Options - System Options - File Locations - Document Templates and assign either ‘C:\ProgramData\SOLIDWORKS\SOLIDWORKS 20XX\templates’ or your custom path.
6. Go to Tools - Options - System Options - Default Templates.
7. For each of the ‘Part’, ‘Drawing’ and ‘Assembly’ file paths, press the browse button.
8. From the folder of the templates, drag every new template in SOLIDWORKS and customize the data in accordance with the need.
Keywords S-071806,1-5F4FBOV

It does not sound so "forward compatible" anymore.

I saw another KB article about sending SW your old templates for investigation to the dev team, as they could cause some apparently known issue. If I found it I would post back here.

[mp3-250]

Found it

Question
In the SOLIDWORKS® CAD software, how do I determine if I am using an old template?

Answer
Making sure that you use the correct template version for your version of the SOLIDWORKS® software is fundamental in avoiding unexpected behavior in the Sheet Metal, BOM, Cut List and other environments.

There is no tool available in the user interface to check the template version. One way that you can do this is as follows:

1. Create a new part or assembly.
2. Select the 'Top Plane' in the FeatureManager®.
3. Right-click and select 'Properties'.

The ‘Date created’ field provides information about the creation date. If the template is very old, consider replacing it with a new template from scratch.

SolidWorks Development staff from time to time redesigns entire areas of SolidWorks software for better performance and stability. SolidWorks will always use the code which features were created in to ensure data parity - to take advantage of the latest and best code SolidWorks Development has to offer, it is recommended to create new templates instead of migrating existing templates to the latest version if you are encountering any faults after a migration to a new version.
Additionally, the old templates which possibly exhibit poor function should be provided to your local VAR (Value added reseller) for submission to SolidWorks for review.

[mp3-250]

so while saying there should be no problem with templates, they admit some problem could indeed arise.

like that time around 2014-2019 when sw was crashing like crazy, but nobody at sw dev team was even aware?
they even said something like "we use sw to perform real world mechanical design during testing phase " and still I modeled a screw, tried to change a color and sw was exploding in my face. I guess it was my videocard driver...

[SPerman]

However, this is not the best or most accurate approach because the save retains the original (old version) structure and does not fully convert the main structure. The presence of old data can influence negative behaviors in Sheet Metal, Cut List and other functionalities.

It is inexcusable that there is no tool to port, or even record, the customizations in your templates.

If upgrading to new templates were easy, think about how much load that would take off of the VARs and programmers. A whole bunch of these issues would just go away, because most people would update their templates when they updated their software.

[mp3-250]

It is inexcusable that there is no tool to port, or even record, the customizations in your templates.

If upgrading to new templates were easy, think about how much load that would take off of the VARs and programmers. A whole bunch of these issues would just go away, because most people would update their templates when they updated their software.

as I wrote in the past there are like 1700 settings inside a single template.
let alone you have to guess where the newly introduced ones are located when you version up SW.

I dump them with macros and some excel sheet i made from info found on api help. it take some day to properly sort and test

[laukejas]

If the templates were such an issue SWX (not DSS) would issue a tool that allows you to create new ones based on the old ones, or to convert/update an "old" template to a new one. BTW, has anyone bothered to write a macro to do this?

Attaching a macro I created for modifying the existing parts/assemblies to the changes I made in my new templates. It's of course very specific to my use case, but you can modify it to your needs.

[Glenn Schroeder]

People from Dassault have told me straight-up that templates shouldn't be an issue and a VAR saying that the template is an issue is generally a VAR that does not want to do the work to find out what setting in the template is causing the specific issue. If your VAR reports back with a "it's your template", get a second opinion from another VAR. That is what I was told by many people including one who works for a VAR when I went to visit them. John Sweeney confirmed it to me, they also built a document to explain how to "update" old templates. Here's the preliminary version of the document they were building, John told me the completed version is pretty much the same.

I have also seen quite a few recommendations to update templates every year. I have ignored that advice. I'm still using templates that were set up in 2009. I don't even bother saving them to the new version unless I make some changes (and I go years without doing that).

I will add that I don't use any type of PDM. That may (or may not) make a difference.

[AlexLachance]

I have also seen quite a few recommendations to update templates every year. I have ignored that advice. I'm still using templates that were set up in 2009. I don't even bother saving them to the new version unless I make some changes (and I go years without doing that).

I will add that I don't use any type of PDM. That may (or may not) make a difference.

I do update them when I upgrade, both to ensure maximum compatibility and also to take notice of whatever has changed, but I don't recreate from scratch my parts and assemblies to have them in the "new" template, which is why I was glad to have someone from Dassault tell me this. If I ever do get a file that becomes problematic in the long run, I'll be able to push 'em around. We've been on SolidWorks since 2012, had issues when moving to 2019, haven't had any 'major' ones in the last few moves. (2021 and 2023)

[TRKemp]

I do update them when I upgrade, both to ensure maximum compatibility and also to take notice of whatever has changed, but I don't recreate from scratch my parts and assemblies to have them in the "new" template, which is why I was glad to have someone from Dassault tell me this. If I ever do get a file that becomes problematic in the long run, I'll be able to push 'em around. We've been on SolidWorks since 2012, had issues when moving to 2019, haven't had any 'major' ones in the last few moves. (2021 and 2023)

The first SW rep that looked at that graphics issue I was having in 2024 with the cone initially blamed it on the "old architecture" of the template it was created in and that it was "concerning" that I was still making parts with those templates. So I did my due dilegence, created a new template from 2022, re-created the part in its entirety and still wound up with the same problem. My VAR resubmitted it after verifying the anomoly still existing on a modern template, and I haven't heard anything back as of yet.

I mentioned to the VAR after the first explanation that "we’ll need to consider no longer upgrading to newer versions to avoid our “old architecture” becoming a liability." But I guess thats still being determined.