Ian Mitchell

[Ian Mitchell]

I think I have fixed this in the latest release 1.3.5.4

[Ian Mitchell]

I have looked at your examples (thanks) and I don’t understand where the issue is.
When I re-generate your document (the ‘Short template..) one, I see a caption under the diagram, as expected.
What are you expecting?
Note: the ‘Preview’ tree view in eaDocX is designed to give you and idea of what your document will probably look like. It will not be 100% the same as the final document, because all kinds of information are left out from the tree view, so that it’s easy to understand. It’s mostly there to see where you have excluded items, and as way to see the overall document structure.
Please cn you provide a simple document which shows the problem (your ZIP file has 3) which show where the problem is.

[Ian Mitchell]

Fixed in 1.3.5.4.
Problem was in printing of tagged values of stereotyped packages. My bad.

[Ian Mitchell]

Fixed in v 1.3.5.4
Thanks for all the information! This really helps me to find the problem quickly.

[Ian Mitchell]

This is a large document, so quite hard to find the error.
I THINK this is fixed in 1.3.5.4

[Ian Mitchell]

As with your other requests, I need an XMI of the content of your test repository.
From what i understand of what you are tryin to do, are you trying to edit the case when two elements are connected by a tagged value? And not by a connector?
If that is so, then eaSheets does not support this use case.
If you would like me to look more into this, then please send the XMI of your data.
Thanks

[Ian Mitchell]

Thanks – I also need the XMI of your model example – I think there are tagged values and other data which I can not reproduce.
Also, how did you create the sheet on page 1? I assume you added some of the columns. Which ones did you choose?
Always better to include an XMI, then I know we are both working with exactly the same data. Also include the Excel versions of any sheets you created.

[Ian Mitchell]

Which version of eaTeamWorks are you using?
This is a class of error where the eaTeamworks code has good error-handelling, but the Sparx API decides to put up an error message anyway.
Does eaTeamWorks continue to work when this happens?
Also, what kind of local repository are you using? EAP/EAPX/QEA/QEAX ?

• This reply was modified 1 month, 1 week ago by Ian Mitchell.

[Ian Mitchell]

eaSheets can show parent/child elements using the option on the menu (Show / Hide element children).
Showing them in a Smart Sheet does not seem to work, which I will investigate.
As for your ‘owns’ relationship, it seems like – from your exaple screen sot – that ‘owns’ is some king of aggregation relationship, not parent child, so I’m a bit confused about what you have in your model, as well as what you expect to see!
Maybe if you provide a little XMI in here, for me to look at? And so you can explain what you expect.
Thanks

[Ian Mitchell]

In the eaSheets menu, choose ‘Show / Hide columns’, then in ‘Advanced’ group you will find Translated name, Translated alias and Translated description (notes).
If you add these to the columns in the sheet, you can then view and update these values.
See https://www.eateamworks.com/eateamworks-help/eadocx/translation/

[Ian Mitchell]

I think this will be fixed in v1.3, available shortly (March 2024)

[Ian Mitchell]

Which eaTeamWorks version are you using?
Please can you provide a test case which I can investigate – I need to know the structure of your data before you start editing, and the steps you used to produce the error.
Thanks

[Ian Mitchell]

This option is still in the Quick Document settings, but it shold hve been removed.
Stopping using this was deliberate, because:
(1) so few people use instances in their modelling, I’m gradually removing support for specific instance types: everything is just ‘Object’, as it is in EA.
(2) this was forst to go, just because formatting an instance of element in the same way as its classifier is a bit strange. Sure, the instance gets a Profile, but why would we print the classifier and its instances the same way? The instances have actual values of the attributes of the classifier, in the Run State Variables, so they shold look very different. This was just a short-cut to providing diffeent profiles for different kinds of ‘object’.
Excessive flexibility.

[Ian Mitchell]

I’ll check the eaDocX meta-data, to see if that’s something that it understands.

[Ian Mitchell]

I don’t know – I’ll have a look

[Author]

Posts