Manual Project Migration

[EricNyh]

I'm having some weird issues with my custom project template that was migrated from earlier versions.

• Things like the BOP/TOP data fields are not populating, so some custom annotations are not working.
• When a project is created the wrong folder paths are created under \ORTHO\.
• I'm sure there could be some other issues I'm not thinking of...

So I was thinking I would create a brand new (and clean) 2014 project, using the stock stuff, then do a manual migration of my custom settings to make a new template project for future jobs.

I'm wondering what information I can take from my old template project (custom stuff) and just copy to my new project - and what needs to be recreated?

Does this even make sense?

[TomislavGolubovic]

I'd create a new project, and base it on an existing template (tick box at the bottom of the 1st dialog box for creating a new project) then see what it brings in. From there, I'd import models as required, if they aren't in there already.

[EricNyh]

That's what I normally do, but my existing template (which was migrated from older versions) has an issue where the BOP & TOP fields are not being populated.

So I was considering trying to start fresh, to fix any issues....but I want to minimize recreating all my custom stuff.

[EricNyh]

So I made a copy of my blank template project (with all my company settings) and then replaced the Piping.dcf file with a clean copy taken from the shipped version.  Then created a new project using my updated company template.

This 'seems' to have fixed the issue where the BOP/TOP data fields were not populating.  Can anyone foresee any issues this might cause down the line?

Regards.