Jason Blewitt

[Jason Blewitt]

Yeah, most of us are on 4.2, although a colleague hit the issue on 4.3.0.3 yesterday.

[Jason Blewitt]

Thank you for getting back to me so quickly. Fully appreciate this won’t be an easy one as this is very far removed from normal processing parameters.

Steps as follows:
– open document set diagram (this contains 10 doc elements)
– right click and choose to generate all documents via menu options
– Choose to increase Build number only
– Generate all

I think we saw the issue before when someone didn’t update the repository location on their machine within the eaDocX repository settings, so that might be one way to duplicate it without needing to rely on an unstable network connection.

It looks as if the connection between the element and the physical file is being lost once eaDocX determines it cannot successfully find / connect to the file. Seems odd at this point that the tool appears to choose to remove the link rather than just stop trying and presenting an error message.

[Jason Blewitt]

Following another full regeneration, this time increasing build number only rather than the minor increment, the element reports have generated.

I’ll keep an eye out and raise a new topic if it happens again and I’m able to provide more information for support.

Thank you for all your assistance so far!

[Jason Blewitt]

I have regenerated a few of the documents individually and they all generate the Element Reports without issue.

The first version of each of the documents is correctly showing the output from the reports, so it does seem a bit odd that only the versions generated as part of the multi-doc generation don’t.

I have since noticed that the first two documents generated have correctly output the report (out of 25).

I’ll try another regeneration shortly to see if it was some sort of temporary blip.

[Jason Blewitt]

The good news:
A full set of 25 documents successfully generated a new version as part of the multi-doc generation.

The bad news:
It appears that Element Reports aren’t being generated when the document is regenerated in this way.

I have two very simple Element Reports in each document; one that pulls out a single Action from a single package and display just the Description. Another which pulls out a set of Actions from a package and displays the Name as a column and the Description as another column.

Both reports work without issue when regenerating a single document.

[Jason Blewitt]

Unfortunately no longer appear to be able use the multi doc generation capability.
Upon installing the latest version of eaDocX and attempting to use the multi document generation capability, I get the attached error.

This error appears when I right clicked on the diagram and selected the following option:
Extensions -> eaDocX -> Generate all documents

[Jason Blewitt]

That’s brilliant, thank you for your help on this!

[Jason Blewitt]

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.

[Jason Blewitt]

Double clicking the <> element opens the document and creates the copy in the OneDrive location as I specified in my previous post.

Double clicking the <> artifact opens the Document Details pop up. I can right click the artifact and ‘open the latest version’ if the document has been created in the OneDrive location. Else it bombs out and removes the links.

From what I can gather, there are two issues:
1. If the document cannot be found, eaDocX removes all document versions from the document artifact. If this is part of a multi-doc generation it also removes all document versions following that document that haven’t been generated yet. This seems like a pretty serious bug given the effort involved in re-adding all documents for a large docco set. Have you been able to replicate this locally (imagine setting up three documents, deleting the physical document for the second document and then attempting to generate all three at once should mimic the situation I’m in)?

2. A file location appears to have been set somewhere which is causing eaDocX to create a copy of the document in an unspecified location, and also looking in said location rather than the configured area as per Document Management settings.

If we can figure out where issue 2 is being set, I can resolve my short term problem although I am very wary about continuing down this path with issue 1 outstanding.

[Jason Blewitt]

Interestingly, I have noticed that if I open one of the document versions directly via EA, (e.g. <> 0.0.1), it creates a copy in the OneDrive location specified above.
It does this for every document I open this way.

Is there a setting somewhere that is being used to control this as it’s not a location I have ever set personally; the folder itself is historic.

[Jason Blewitt]

Using option 2 for DM.

The location of the ‘un-found’ documents appears to be going to an old OneDrive folder: ‘C:UsersUserOneDriveDocuments’

The actual location the documents are stored is on a shared drive in a folder named ‘Documentation’.

[Jason Blewitt]

Okay, bad news first:
I’ve attempted a regeneration with two documents and that worked fine, but when I attempted it again with five I got the original error with the loss of documents.

Good news:
I can replicate the issue with ease as it actually appears to be certain documents which cause the error. It looks like with certain documents, when eaDocX attempts to find the document, it looks in the wrong place. As it can’t find the file, I get an unhandled exception and lose any document from that point in the generation process forward. I.e. when it error’d on document 3, I also lost 4 and 5.

I took this test one step further by adding the document back into DM and testing if I could re-open the document. If I attempt to open the document by choosing the specific version, it opens fine within eaDocX as desired. If however, I right click the Document artifact and request to open the latest version, eaDocX looks for the document in a different location to where the document is stored, can’t find it, so errors again and loses the versions as above.

All these templates were created in the latest eaDocX version in the same way:

1. Select to create new document from with eaDocX
2. Import eaDocX profile
3. Apply company styling
4. Add reports (same across each document)
5. Add packages for extraction (same model just different packages for different areas)
6. Regenerate in local Documents folder
7. Add to DM

Therefore I can’t see why eaDocX attempts to look in a different location for certain documents. Any ideas?

[Jason Blewitt]

I haven’t attempted to redo the documents yet as I was hoping for a way to restore the links.
I’ll work through getting a couple back in this morning between my regular work and see if I can replicate the problem.
There were no other documents open at the time so I do wonder if it was an access issue.
I have full admin rights to the model and the database it is stored in so unlikely to be a permission issue, wonder if it could be something to do with access to the shared drive where the documents are stored momentarily dropping.
Will see what happens and get back to you.

[Jason Blewitt]

I have the same issue as mentioned above, however when this occurred it also wiped out all links to the documents within EA. All I’m left with is the high level artefact within nothing underneath it.
Is there any update on this problem?

For assistance, I’m using:
EA: Version 12.1.1230
eaDocX: Version 4.1.6.6
Word: Office 365

The templates were freshly created and had all generated successfully when done one at a time. This issue occurred when I attempted to use the multi-doc generation.

[Author]

Posts