Products

Home Forums eadocX Support

Forum Replies Created

Viewing 15 posts - 166 through 180 (of 1,235 total)
  • Author
    Posts
  • in reply to: Failed to open document #9023
    eadocX Support
    Participant

    which eaDocX version are you using? In the very latest version (3.9.5.7) I skipped this piece of code. So please download the latest version, and try that.
    The installation tester exercises the main Word interfaces which eaDocX uses, but doesn’t try them all – there are just too many.

    in reply to: Failed to open document #9021
    eadocX Support
    Participant

    This means that eaDocX can’t find the Word Interop DLL which it expects to find in your installation of Office.
    Try a repair/re-install (not a full-reinstall) of Word – this sometimes gets the office DLLs correctly setup.

    in reply to: Links are not working in script generated contents #9035
    eadocX Support
    Participant

    I can’t remember is we publish the format for eaDocX hyperlinks. It’s certainly not like the one above. Can you look at the example scripts? If there is an example with the hyperlink format in it, then use that as a pattern (can’t check as I’m out of the office right now)

    in reply to: Links are not working in script generated contents #9032
    eadocX Support
    Participant

    Are you trying to add eaDocX hyperlinks into your scripted output ?

    in reply to: eaXL Child Attributes #8960
    eadocX Support
    Participant

    we are aware that the treatment of child elements, and other sub-elements, in V3 isn’t complete – we are looking at it for V4, currently under development. There will be no change to the V3 function in this area, so please make the best use of what there is until V4 is available.

    in reply to: Loaded Profile settings are overwritten #8958
    eadocX Support
    Participant

    this has been put in the backlog for V4, so won’t be fixed until that is available.
    And no, I don’t know when that will be.

    in reply to: Adding child elements via Excel import #9014
    eadocX Support
    Participant

    The use case you are trying to use is not currently supported by eaDocX/Excel.
    I will add it to the backlog of requests for v4, which we are currently designing: what you want to do seems like a very reasonable thing!

    in reply to: Failed to validate key #9005
    eadocX Support
    Participant

    As previously described this error arises due to an incompatibility between one of the Windows updates and our crypto software running eaDocX Floating Licences.
    We have worked to find a resolution for this for many months, but have not been successful.
    So we can offer you 2 alternatives:
    Either exchange your floating licence for standard licences (4 standard for 1 floating)
    Or if you want to retain a single key for your team, exchange your floating licence for an organisational (group) licence.

    Please let us know which you prefer.

    Detail of Organisational licences can be found online at https://store.eadocx.com/web-downloads/organisational-licence

    Best regards

    in reply to: Object reference not set to an instance of an obje #9510
    eadocX Support
    Participant

    Might be an inconsistency in the EA model.
    Try exporting the package as XMI, deleting it in the model, and re-importing.

    in reply to: Object reference not set to an instance of an obje #9508
    eadocX Support
    Participant

    I think I need a bit more than this if I’m going to look into this.
    What database? Do you have sample data you can send me ?

    in reply to: Failed to validate key #9003
    eadocX Support
    Participant

    This is a fatal error as far as using the eaDocX floating licence is concerned. As documented elsewhere, we have no fix for this, nor any proposed fix.
    You alternatives are either to (1) swap floating licences for fixed ones 1:4, or (2) use an Organisation a licence. Please contact support@eadocx.com

    in reply to: Excel upload adds non printable chars #9009
    eadocX Support
    Participant

    We strongly suggest that you do NOT use eaDocX/Excel for editing ‘notes’ fields of ANY element type.
    The EA content is stored in a non-standard, not well-formed HTML-ish format, which gets all kinds of odd characters added.
    It seems to just-about work when notes are read then written back, but editing seems to cause issues.
    We’ll look again at this in V4, currently in development

    in reply to: Sorting order in section #8981
    eadocX Support
    Participant

    It should be the same as the order from EA. Remember that the Ea sort order is only set when you move elements up+down – otherwise the sort isn’t saved in the DB.

    in reply to: Messages of a sequence diagram not printing #8977
    eadocX Support
    Participant

    I removed this from recent release in error – whoops.
    Put back into 3.9.5.4, now on the website.

    in reply to: Project Glossary- eaDocX does not generate content #8714
    eadocX Support
    Participant

    please can you email a SMALL EAP file, and your document, to support@eadocx, and I’ll take a look.

Viewing 15 posts - 166 through 180 (of 1,235 total)

Compare licence prices

Choose the licence that’s right for you and your team

Prices

Download a free trial

Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.

Download