Ian Mitchell

[Ian Mitchell]

HI James,
At what point does this message appear? When you try to open the repository in EA?

[Ian Mitchell]

If you choose to print the elements type as ‘Inline’, then choose ‘vertical table’, that should do it. Not sure about printing the ‘notes’ of a TV though….

[Ian Mitchell]

Ok – you lost me at ‘multi-user EAPX’ : this isn’t supported by Sparx, or by us, so sadly you’re on your own. Yes, I know it works – mostly – but these locking issues are what makes it an un-supported configuration.

• This reply was modified 2 years, 7 months ago by Ian Mitchell.

[Ian Mitchell]

Making good progress on the 64 bit version. But EA V16 comes with a new type of DBMS, to testing that as well. There is a V5 64-bit verison now on the website – please try it and let me know how it goes.

[Ian Mitchell]

Hi Steve,
We are still testing eaDocX with QEA files – there are some differences in the SQL they accept, which seems to be different from all other DBMSs.
We are also having other issues with EA V16, so we are planning to do more testing to resolve these issues.
In the meantime, I suggest reverting to EA 15.
Thanks

[Ian Mitchell]

When I look at the error, this is coming from a call which eaDocX makes to Word, so if there is a restriction, it must come from Word.
I have tried to replicate this error, with element names of 256 characters, and it is ok.
Are you still using Arabic characters ? My test envoriment is a simple ENG/UK language.

[Ian Mitchell]

This seems to have become a general-purpose thread 🙁
@Marie – eaDocX does not support arabic text – I have no way to test it, or to debug any issues you have with it, as I am not an arabic speaker – sorry!

[Ian Mitchell]

If you zip the repository, and send it to me via WeTransfer, then I will look at your issue. Send it to ian@eadocx.com

[Ian Mitchell]

It sounds like there is either (a) an issue with the EA content, or (b) eaDocX has found something in the model it doesn’t understand.
If (a) then run the EA Integrity Check (in V15: Configure / Model / Integrity check) which can find errors. If this does not work, then export a large part of your model to an XMI, delete that part of the model, then re-import. This removes all kinds of errors.
if (b) then I can only look into it if I have some sample data to work with.
Thanks
Ian

[Ian Mitchell]

If you can send me a small XMI with the data which makes eaDocX fail, I will have a look at it. The data probably just has a state which I have not seen before.

[Ian Mitchell]

Does this happen for every kind of Quick Document? Or just on one part of your model?

[Ian Mitchell]

Hi JD,
I have run Model Expert with EA16. The only outstanding issues I have with it are stability (occasional, un-characteristic crashes) and with accessing the new QEAX database, which seems to have a few funnies (MX has A LOT of SQL…).
I have also only run it with the 32-bit version.

[Ian Mitchell]

You are quite correct!
Issue has now been fixed in v5.0.5.9, now on the website. Sorry about that.
You might like to know that we plan to retire some the document management functions of eaDocX in V6, specifically:
– assigning people to document roles
– definition of those roles.
– ideas about approval and sign-off of documents.
Our research indicates that organisations who need this kind of function use dedicated document management systems, and use eaDocX to just create the documents, not managem them.
If you want to know more, please contact me..
Ian

[Ian Mitchell]

Noteice that it has to be a Named Range. That’s something you do in Excel: i think you just select the area you want, then right-click and choose ‘DEfine Name’, or something like that. Then eaDocX will use that name to fetch the data and put it into the report.

[Ian Mitchell]

Hi Mike,
I’ve reproduced the diagram you posted above, and re-created the same document you see, so we’re both on the same page.
Albeit not the page you want to be on…
To re-create your example, I told eaDocX to print each of the TVs by name, for any InterfaceBlock element. Whic is all that eaDocX allows us to do.
There is no way to say ‘only print non-inherited TVs’, or, ‘only print the TV with where an element has it’s own value for it.
I think that maybe what you are asking for is a more generic feature, which says ‘print all my Tagged Values’, with a further option to ‘print TVs specific to this elemnt’ or the opposite ‘print TVs INCLUDING those I inherit’.
Is this what you need ? Or am I missing something?

[Author]

Posts