Ian Mitchell

[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 11 months, 3 weeks 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.

[Ian Mitchell]

Hi Paul,
Have you tried this with V6?
If it’s an issue in V6 as well – which it it propbably is – then any fix will only be to hte latest version – current V6, in eaTeamWorks V1

[Ian Mitchell]

Sorry for the late reply – holiday season in UK.
Please can you download the latest version of TeamWorks? I have made some changes to the Licence Manager. Version 1.0.5.0 is now on the website.
Thanks

[Ian Mitchell]

We made the mistake of asking the web team to put a bit more security into the reg/login process. Looks like they over-delivered. Thanks for the tip – I’ll look into it.

[Ian Mitchell]

Hi Marc,
We have just announced (19th June 2023) that Model Expert is now being delivered inside the ‘eaTeamWorks’ product: your old key will still work, so you need to download eaTeamWorks to get a 64-bit version of Model Expert.
I’ve not had any problem installing 32- and 64-bit version of addins on the same machine. They seem to play quite nicely.
‘hope this helps
Ian

[Ian Mitchell]

Again, I need more detail in order to investigate this:
what does this bit of your model look like
– exactly what are you trying to do

[Author]

Posts