We are working in the InCopy workflow with an off-site design group. Occasionally, we get reports that they are unable to relink indp files we have sent back to them from InCopy. Just so we understand the process, we have tried to replicate what we think the problem may be. This has led to some questions on our part regarding the InDesign part of the process. Here is what we have discovered so far.
If the InDesign file from which the InCopy package was issued is moved to another computer, the indp file will not link up with the copied file. This is true even if the InDesign assignment folder is moved along with the original InDesign file. At first the message appears:
The package file contains an assignment that doesn't exist in "filename.indd". Your package file may be out of date or associated with a different document. How do you want to continue? Browse to locate the correct document. or Save the contents of the package to disk.
If you select browse to locate..., and if you select the copied file, a loop results.
From this, it would seem that InCopy workflow recommends that InDesign files not be moved and that the InDesign assignment folder be saved in the same folder as the InDesign file and not moved. Is this the recommended practice?
For InDesign files that have moved, what is the workaround, if any, for relinking the returned indp file?
Terry