Ian Mitchell

[Ian Mitchell]

I thought that Start- and End-events are just stereotypes of Event (or, as it’s BPMN, maybe stereotypes of Class..) To get their constraints and internal requirements, just add those from the ‘subelement’ tab.

[Ian Mitchell]

Hi Marie,
Thanks for the test file. Good idea to send it as a Zipped .txt file – I just renamed it to .XML, and it loaded fine into my PostgreSQL test database.
Just like when you loaded it into a new repository, it seems to create the dashboard OK. I tried to create a meta-model diagram from the dashboard, and there was a temporary error, but then it displayed OK.
BUT
…your test data didn’t touch quite a lot of the function Model Expert, as there are no connectors.

When a package creates errors like this, but then they go away when the package is exported and re-imported into a new repository, this shows that there are low-level inconsistencies in the source data. Lots of these are easily removed using the Ea built-in EA integrity check (Configure / Model / Integrity / Project Integrity), but it doesn’t find everything.
Taking a backup, exporting the package to XMI, deleting the package, then re-importing it works well, though beware if the package is heavily liked to other parts of the model.
Less dangerous way is to try Model Expert on sub-packages, and see which one creates the error, then repeat the steps above on a much smaller scale.
I hope this helps
Ian

[Ian Mitchell]

All users of EA must install Model Expert on their own machines.
Sorry if this was not clear in the help.

[Ian Mitchell]

where does this appear? At install time ?

[Ian Mitchell]

Thanks Marie – is it possible for you to post an XMI of one of your packages which shows this error? I tried it on a few test cases, but your data is clearly a bit different from all of them! Please remove any confidential data from the XMI – I just need the structure.
Thanks

[Ian Mitchell]

OK – found the problem. Seems like postgreSQL does casting of variables slightly diffrently to SQlServer and the other DBMSs.
I THINK I have fixed this, but I haven’t tested every bit of SQL, so please re-post here is you find any more issues.
Sorry for the problem – issue is resolved in v2.2.3.0, now available for you to download.
Ian

[Ian Mitchell]

Hi Marie
This looks like an incompatibility between DBMS types – it always seems to be postgrSQL which causes the problems!
I am investigating….

[Ian Mitchell]

see reply to this latest post in another thread.

[Ian Mitchell]

Yes – you need a full version of MS Word installed on your computer. Ofice 365 subscriptions are OK, but you must have the option which installs all the software on your machine. Web-only versions won’t work, as eaDocX must talk to the Word API, which is provided only in full Word installations.

[Ian Mitchell]

Hi – please you submit this to the Model Expert forum

[Ian Mitchell]

I have added a fix, so that you can introduce a new document into eaDocX by just setting ‘Use Document Management’ in the document settings.
This is available now in v5.0.5.4
Thanks

[Ian Mitchell]

I will investigate

[Ian Mitchell]

Sorry, but I still don’t understand what you want.

[Ian Mitchell]

I understand WHAT you want to do.
I don’t yet understand WHERE you want to do it. Is this a stand-alone table, or a table which is part of something else?

[Ian Mitchell]

This function gets around a restriction in MS Word. In older versions of Word, when using the HTML interface, Word does not allow style names which contain spaces.
So, as a work-around, eaDocX changes the name of the style in Word to add underscore instead of space (and adds “_eaDocX_” so that it’s easy to find again) then, when the document has generated, changes the name back to the original.
Here, it looks like something has happened at the end of this process, and the document has not completed the generate, and the final ‘change back’ function has not worked.
Did you see any errors when generating?

[Author]

Posts