Ian Mitchell

[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 4 weeks 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

[Ian Mitchell]

try ian@abilityengineering.co.uk

[Ian Mitchell]

HI Mark,
Please can you email me some example data which shows what you’re doing, and I’ll try to reproduce what you’re trying to do.
Thanks

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

[Ian Mitchell]

Hi Marco – I think this is fixed in the latest release – I agree there were some problems in saving settings.
Please can you check it’s ok for you in v 1.0.8?
Thanks

[Ian Mitchell]

There’s now an article which explains all this. See https://www.eateamworks.com/easheets/resources/insights/template-elements/

[Ian Mitchell]

If you just open the package which contains the Application Components as a ‘Smart Sheet’ (right click on the package, then Specialize / eaSheets / Open Smart Sheet), then eaSheets will find ALL types of elements related to each Application Component, and create column in the sheet for each one.

If there are currently no related elements, then you can use the idea of a ‘Template Element’.
This means just creating an Application Component, with all the relationships you care about – it can be a dummy compoment, which you only use for this reason- and putting it into the package.
Then, when eaSheets opens the package, it will automatically populate the columns you need.
There will be some more information on this technique on the website soon – I will update this post when it’s written.

[Author]

Posts