Okay I have figured out how to circumvent issue 2 by amending the eaDocX Application Repository settings to change my ‘Personal folder’ in DM to also point towards the shared network drive location.
This currently appears to be preventing eaDocX from creating copies of the document in an incorrect location and then falling over with issue 1 during the multi-doc process (attempted with a set of 4 documents, only increasing the ‘build’ number).
Despite this, I unfortunately can’t really use the multi-doc generation process to its full potential until issue 1 is sorted as the risk and overhead is too great with the size of the document set I’m working with (circa 50 documents).
Can you confirm if you have been able to replicate the issue and if so, whether a fix would be in the works any time soon?
Thanks.
