we work with Publisher 2013 and Vault Colaboration 2013.
When inserting assemblies from Vault we get a lot of unresolved file messages.
All the unresolved files are correct downloaded from Vault to Workspace (local), but we have to click through the file path manually and show Publisher where the files are located! If we skip, these files are not shown!
Does someone know this Problem? How to solve? Are there additinal settings in Publisher?
Thanks in Advance!
What is the result if you insert the file from local (Vault workspace)? will there still be unresolved file messages?
If yes, then the source file must be updated to correct the file relationships.
if no, then it might be a Publisher issue and download the vault files and insert from local would be a work around.
first of all thanks for your quick response!
The workaround you mentioned is working!
When inserting the *.iam from local I can tell the publisher which projectfile to use => All parts are inserted correct!!
Where can I tell the publisher, when inserting from Vault, which projectfile to use?
I think that would solve the Problem!
Our collegues that are using Publisher have no Vault. The only have the publisher installed. So the have to "Insert from Vault" to get the files downloaded to local.
Well, Insert from Vault does not has that option to tell which project to use.
I have logged a issue in our internal tracking system.
obviously it is ESSENTIAL to specify the project-file, while working with assemblies stored inVault!
Our Documtation-Team is very happy with the features of the publisher.
But all datas are in Vault, so in our mind, it has to be a MAJOR-Feature to get the datas proper inserted.
This is for us a very important subject!
Please keep us informed!
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.