TomMalinski
Mechanical
- Aug 5, 2010
- 24
Can anybody tell me if after migrating from PDMW to PDMS that file references all work ok?
My VAR has written their own migration utility that migrates files from PDMW to PDMS with all history revisions and versions in tact. This is great, however assemblies that have references to files in sub-folders are broken in the process. while doing test migrations when I open an assembly from my PDMS cash, it cant find referenced files that reside outside the parent folder of the assembly. They have a custom ADD-IN they wrote that fixes this (post) after Migration, where a user opens up a job / Assembly and it locates the missing references automatically. The user then saves the assembly and all references are fixed. The problem is we have to go thru every job in the vault one at a time so the add-in can do its thing. Further complicating this issue is users with a contributor license that do not have SolidWorks installed cannot use the add-in that runs within Solidworks. This will require a SolidWorks user to process every job in the vault cash immediately after migration to be sure all referenced files are working ASAP.
So my question is did SolidWorks supply VAR's with a basic utility that works even though it won't migrate history? More importantly are the references to files in sub-folders in tact?
Any possible solutions out there?
Thanks
Tom
My VAR has written their own migration utility that migrates files from PDMW to PDMS with all history revisions and versions in tact. This is great, however assemblies that have references to files in sub-folders are broken in the process. while doing test migrations when I open an assembly from my PDMS cash, it cant find referenced files that reside outside the parent folder of the assembly. They have a custom ADD-IN they wrote that fixes this (post) after Migration, where a user opens up a job / Assembly and it locates the missing references automatically. The user then saves the assembly and all references are fixed. The problem is we have to go thru every job in the vault one at a time so the add-in can do its thing. Further complicating this issue is users with a contributor license that do not have SolidWorks installed cannot use the add-in that runs within Solidworks. This will require a SolidWorks user to process every job in the vault cash immediately after migration to be sure all referenced files are working ASAP.
So my question is did SolidWorks supply VAR's with a basic utility that works even though it won't migrate history? More importantly are the references to files in sub-folders in tact?
Any possible solutions out there?
Thanks
Tom