eadocX Support

[eadocX Support]

The location which is in the eaDocX Document Management settings just says where to put new documents.
Once you have done that, then the <>Element can then be put anywhere in your model. As new versions of the document are created, eaDocX will find it.
So you can have a meaningful organisation of documents, just as you suggest.

[eadocX Support]

We don’t seem to have any control over stuff like this. There are other ‘helpful’ timeouts and timeout warnings in COM (the deep techie bits of Windows) which we’ve tried over the years to investigate, but always reach the same dead-end.
When we test the scripted generation, we only use a few fairly simple cases, where the script makes a couple of calls to EA, and does some simple formatting. We never intended it to do serious number crunching, or large numbers of EA calls.

[eadocX Support]

I’ve been trying to reproduce this error, but currently with no success.
I can think of no reason why Element Report would not be re-generated, except where they were either not in the version being re-generated, or do not have a Profile for the elements in the report.
I’m looking into both of these. They MAY be some cases where, if you edit a document to add a new ER section, but don’t save it, then the re-generate won’t pick up the changes.

[eadocX Support]

Ah – rats – forgot I added a new bit of UI, so should have changed the installer.
New version – 4.1.7.1 now on the website – sorry about that.

[eadocX Support]

OK -fix created, and now on website as 4.1.7.0. I’ve added more checking for non-existent documents (though this was not the issue)

[eadocX Support]

Working on a fix now. Will advise when it’s available. Seems like there were nested errors, which cancelled each other out in my test cases.

[eadocX Support]

None yet.
Sorry.
Unbelievably hard problem to fix.

[eadocX Support]

Can you double-click on the <> and open the document ?

[eadocX Support]

OK – this is progress.
Can you tell where the ‘un-found’ documents are located?
eaDocX gives you two options:
1 – keep them as .docx Word documents on a drive somewhere
2 – save them directly into EA (they are element.files of the eaDocXVersion elements)
Can you tell which one you are using?
For documents using (2), look in the Properties, in the Files section (can’t remember where this is in V12) and their should be a file like (mydocument name)(my version) – type=”Internal”
For documents using (1) approach, there will be a different entry in ‘files’, with the name of the external file and its location. Type = “Local File”

[eadocX Support]

I think the DM fix I added in v4.1.6.7 fixes this. If not, please let me know.

[eadocX Support]

I don’t think this is the same issue as the one you referenced – that was on a much older eaDocX version.
I’ve tried to re-create your issue (with just 2 docs, not the full 25) and I can’t get it to fail..
…except, when doing it repeatedly, the documents were already open in EA/eaDocX, so I had to keep closing them, or I got all kinds of errors. But this is the case for any eaDocX document -they don’t like two copies of the same document opened at the same time.
I can’t see anywhere in the code where we delete all the previous document versions: this multi-generate just adds a new version to the existing document.
Only things I can think of are maybe some permissions issues in your model?
Can you re-try it with just two documents? I can email you my test case as an XMI (tiny stand-alone example) and see if that works for you? send a mail to support at eadocx dot com.

[eadocX Support]

My first suggestion is to get it to work OK using just Word – no eaDocX.
If you happy that the style is OK, then try to get eaDocX to use it.
Do you do this already ?

[eadocX Support]

Well, not so much as bug, more of a special feature!
Seems like all my test cases I use an EA setting (in the EA / Start / View / Preferences window, the Diagram / Diagram Frames / On clipboard images = un-ticked.
This means, I NEVER get the frame.

But, when I check that EA option, I also get a missing right-hand side of the frame.

If I copy the diagram directly into a Word document, then the border is complete. But If I take the eaDocX version of the diagram image, and paste it somewhere else, then the right border is still missing. This suggests that it got missed-out when eaDocX got the image from EA.
All of which is a long way of saying that, IMHO, this is an EA bug, but I wouldn’t bet the farm on that….

[eadocX Support]

I’ve just re-factored the scripting mechanism, but it worked OK with PostGres before I did this.
The 99 error is just that: your script which worked OK in EAP doesn’t with PostGreSQL.
I suggest that you test the script with fixed GUIDs (not passed by eaDocX) and run the script from within EA scripting, and see if that works.
I will release the re-factored scripting support in a future release, as it probably won’t fix your problem.

[eadocX Support]

From the video you sent, it looks like you are using an old version of EA. I also don’t understand why you have only eaXL in your addins – our installer adds both eaDocX and eaXL.
Also, which version of eaDocX/eaXL are you using?
I’ve just tested this function, and it’s OK here – with EA 14.1 and eaDocX 4.1

[Author]

Posts