Thanks for the support Alessandro, It's been invaluable to me trying to resolve this problem. I will investigate the possibility to rebuild the assemblies otherwise I will try to find a way to copy this CC folder to the users local cache.
Finally, on this subject of the files in the workspace. If I combine the CC folders to one folder so we only have one ipt for each existing CC part am I correct that the assemblies will resolve themselves automatically this way?
If you mean rebuilding all the assemblies having the new path to the Standard Parts files in the Workgroup Search Paths and the path to en empty folder for the CC Files, in the active project, before to set the new path for the CC Files as well.
In other words, if you want to apply the latest procedure you have done manually, to all the assemblies and in batch mode, in theory there is no problem for doing this with Task Scheduler.
After setting the project as discussed, close Inventor, start Task Scheduler and select from the Create Task drop down menu, Migrate Files.
Select the project and set the option as in the image below.
After completing the “Migration" and if the log file confirms you that the procedure was successful, restart Inventor and set the new path to the Standard Parts files for the CC Files as well.
Of course, the question is if you can do it with the assemblies set as approved in your PLM.
About the last question, if you decide to go for the workaround to copy the Standard Parts files in the workspace for opening these assemblies, yes, combining them in one folder removing the duplicates should work fine.
Of course, the same files, under the CC Files folder should keep the original structure, for the new assemblies sake.
I do not think this procedure would be possible due to the way we extract the files from the PLM external to the CAD software.
example: ASM= DOC00001234
When extracted from the PLM they are renamed 1234567, 2345678, 3456789 etc.
The links are effectively broken. I may be able to do it manually through the CAD with special privileges but I need to check this.
When I migrated I did not use the standard project file. I created a project specifying a workspace where all these files were stored. I left the content Center as default. These were the settings in the options for the migration.
Should I have put the new CC folder location in the project file when migrating the assembly files?
Thinking out loud here.....
If I was able to extract just the IAM files related to the CC parts would I be able to rebuild them with the tool you supplied Alessandro? I know I would have unresolved assemblies as all the part files would not exist but would that work in theory?
I guess I could test myself.
My last suggestion was just for automating the procedure below:
And you have answered:
“Done, opened OK. save, opened with CC to L: and confirmed opens OK”.
As you wrote, if this or the tool I’ve sent you can be applied to the assemblies in the PLM, it is something you have to try.
If not, I think you should go for the workaround discussed.
I think it is clear for me now how to proceed. Well I have 2 options at least I believe.
I just ran a test of the process you describe above.
I used the Task Scheduler to refresh standard components. As part of the test I deleted the part files from the workspace to simulate an extraction of just the iam files.
With the project configured as you describe I ran the task. After I was able to open the assembly automatically other than the expect resolve link for the part files. I restored these and saved the IAM. I then changed the project file to make the correct CC location. The IAM opened perfectly.
I did the same test as above but I renamed my IAM to simulate the extraction from the PLM. I did not open the assembly within inventor after this time. I changed the Project to my desired settings with the CC as I want it. I then opened the assembly and had to resolve the link to the CC parts.
I am sure you knew this would happen......
So I can use task manager to correct my files but I have to open each assembly after to save it seems (Is rebuild necessary?) Can I create a custom task to automate this process for all my IAM files? I would need to suppress the resolve link to part files though to do it with just the assembly files I believe?
I guess I am asking too much but maybe you can confirm.
I’m sorry, but I’m not sure I’ve understood what you have done exactly.
Please, find my comments below.
“So I can use task manager to correct my files but I have to open each assembly after to save it seems (Is rebuild necessary?) “
If I’ve understood this correctly, you have to do it because you have deleted the part files from the workspace. The Rebuild is recommended.
“Can I create a custom task to automate this process for all my IAM files? I would need to suppress the resolve link to part files though to do it with just the assembly files I believe?”
I think the problem here is exactly the resolve link dialog you get due to the fact you have deleted the part files from the workspace.
I believe you can find on the web some tools that you can easily programming for pressing the Skip button when you get the dialog.
If you find one of these tools, the Task Scheduler process is automatic by definition.
I hope I’ve answered to your questions.
I am running a test now using the task scheduler. I am using a sequential task to first run the refresh standard components and then update design. I used the project file configured with the empty CC as our discussions. For the update design process I selected rebuild and also skip unresolved references.
the process is taking some time because it running through all the CC files due to them being in a workpath.
I may be way off with this test but I thought it was worth a try
I’ve received an internal notification you still need assistance for this problem.
I think I’ve provided all the suggestion I could for resolving or, at least find a workaround for it, considering the specificity of your working environment.
By the way, if you think I can still assist you on this, please, let me know.
Thanks and regards,
Your help has been fantastic. Sorry if this flagged up an aleart for you. You help has made my understanding a lot clearer but I guess the issue is still not totally resolve which is why I clicked no.