Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Uffe

Pages: 1 ... 5 6 [7] 8 9 ... 85
Bugs and Issues / Re: Custom Script fragments not working in 13.5.1352
« on: April 19, 2018, 07:04:58 pm »
... which would seem to indicate that in the last five years there have been 4,983,282 issues.

That's got to be more than 10 per SLOC. Impressive in its own way. ;D

Bugs and Issues / Re: Custom Script fragments not working in 13.5.1352
« on: April 19, 2018, 07:00:23 pm »
Issue confirmed (again), new number 18038572.


Will need to test all my templates to make sure nothing breaks.

Here's a tip: test them twice.

When upgrading 11.1 -> 13.5 I tested mine just once and they worked, but then it turned out they only work once per session.
Also, some users can't generate documents anymore. So test using a few dozen different user accounts too.


Bugs and Issues / Re: User requires ALTER permission on t_image
« on: April 19, 2018, 06:13:59 pm »
The following fix works for 13.5.1352.

Code: (SQL) [Select]
USE The_database_name

GRANT ALTER ON [dbo].[t_image] TO [The_user_name]

Note that you need to grant the ALTER permission to every user in the database. We're using group-based logins and users, but if you're using individual logins/users per modeller, you'll have to grant the permission to all existing users, and remember to grant them when adding new ones as well.


Bugs and Issues / Downgrading from 13.5
« on: April 18, 2018, 01:33:44 am »
Hi all,

After our recent upgrade from 11.1 to 13.5, we've noticed multiple issues with document generation and database modelling, where things that worked in the older version no longer do in the new. We're getting nothing back from Sparx support, so we're going to have to look at downgrading.

We've upgraded all our databases (SQL Server) to the 1220 version of the schema. This means downgrading to 12.1 should be OK, but I'm thinking about what we'll need to do if it turns out the bugs that are causing our problems were already present in 12.1, meaning we'll have do go even further back to either 12.0 or 11.1, where we know things work.

Does anyone have experience of downgrading past a schema change?

Or is it possible to run 11.1/12.0 on a 1220 schema?



Hi Peter,

Seems the document generation took a pretty severe beating in v13. Since upgrading from 11.1, I'm seeing custom fragments fail when invoked through the API (an old bug that had been fixed), and some of my users are unable to run a document generation script that works perfectly for others (well, except for only working once per session due to the first problem).

On March 27th I provided Sparx with an MDG Technology and test project to bughunt the first one, but I haven't heard back since. Regarding the critical problem with certain users being unable to run certain scripts I haven't heard a peep since my report a week ago. In fact, right now I have eight registered bug reports from as far back as March 22nd where I've only received the automated reply.

But hey, it's only half my business analysts who are up in arms. You know, the ones with a lot of say in what tools get used enterprise-wide? Yeah, them. Turns out they don't think calling a colleague to run a script for them three or four times a day is an efficient way of working.

Who knew?


Update: I'm in communication with Sparx (on a 24-hour roundtrip). Use of their logo is an unequivocal No, so I'll need to redesign my icon. No biggie.

I'm more concerned about whether or not I'll be allowed to call the VS project type "EA Add-In," which seems to be prohibited by the legal guidelines.
I'm hoping they'll say Yes; if not, there doesn't seem to be much point in releasing this thing.


A change to a stereotype is not trivial and should only be made after well thinking about it, never on the fly.

Now, someone who is somewhat familiar with EA might be forgiven for thinking that a stereotype's name is not its identity, since that's how most of EA works, but with stereotypes the (fully-qualified) name is in fact the identity. So you can't change it, what you're doing is deleting one stereotype and creating another. EA has no record of the change, and in fact no concept of a stereotype name change.


General Board / Re: Displaying A Banner When Accessing A Model
« on: April 17, 2018, 10:26:12 pm »
I did consider using the default diagram but I cant stop people from changing this using the EA permissions.

If you use shortcut .EAP files, I believe you can specify which diagram to open in the shortcut. Of course, that only applies to people using the shortcut, but if that's what they do then that should work.


General Board / Re: 'Link' Connector type - did I imagine it ?
« on: April 17, 2018, 12:12:46 am »
Hi Ian,

There are Links, and you can connect two Objects with one, in 13.5.


... any chance of a RegisterRASAsset() call making an appearance as well...?

Great, thanks! :)


Will do. I'm still waiting for Sparx to get back to me about the use of their logo, but I've given them a poke and we'll see what happens.

Meantime, there's always user documentation to write. :-\


Bugs and Issues / No API documentation for Repository.ImportRASAsset()
« on: April 13, 2018, 06:34:55 pm »
Hi all,

There is no documentation in the user guide for the automation function Repository.ImportRASAsset(), which was introduced in 1308.

According to EA's VBScript IntelliSense it takes eight string parameters, which takes a bit more effort to work out through trial and error than I would like to spend.




The operation which a CallOperation action calls is stored as the action's classifier, enabling you to locate the operation from the action (in a diagram) by hitting Ctrl-Alt-G.

What complicates matters is that EA actually stores an element's classifier in two ways in the database -- t_object.Classifier holds the classifier's element ID, which is an integer, and t_object.Classifier_guid holds its GUID, which is a string.
Only t_object.Classifier is reflected in the API (Element.ClassifierID), and it's only valid for elements whose classifier is another element (eg Objects). t_object.Classifier_guid, which is used for CallOperation actions, cannot be retrieved through the API.

Instead, you have to go to the database. To retrieve the operation, do something like

Code: (VBScript) [Select]
queryResult = Repository.SQLQuery("select Classifier_guid from t_object where Object_ID=" & element.ElementID)

' You'll need to parse the returned XML text here. A quick and dirty way in this case, since you know
' there should be exactly one result and the tags are always the same, is a hard-coded Mid() call.

methodGuid = Mid(queryResult, 120, 38)

method = Repository.GetMethodByGuid(methodGuid)



Pages: 1 ... 5 6 [7] 8 9 ... 85