Book a Demo

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 - Geert Bellekens

Pages: [1] 2 3 ... 902
1

That actually does not works on my side  but does it means that Azure Image collection content (or at least the few dozens images I need..) should be loaded in IM one by one after being converted ?
 :o

Eric
Yes, I think so. It's been a while since I played with images in shapescripts.
In general I prefer to draw my igages with an actual shapescript and not use those images. They tend to slow down loading a diagram if you have a lot of them.

Geert

2
Eric, there are two types of "images".

The icon you assign your stereotype. That will be shown in the toolbox and project browser
And then the image you want to show on the diagram.

That is actually set in the shapescript.
Assinging an image to your stereotype element doesn't have any effect in your MDG.

Geert

3
Hi Mikael, kind of late to respond, but I wanted to add that Prolaborate has a Versions Explorer mechanism which can be used to show the different versions of your EA model for Prolaborate users.

https://prolaborate.sparxsystems.com/resources/v5-documentation/version-explorer

The caveat is that it requires each version of the model to be maintained in its own separate repository. Not sure if it fits your use case, but figured it was worth mentioning.

Nabil
Nabil,

Have you really tried to use that feature in the real world?
In my experience, clients who purchase Prolaborate are larger organizations that generally use a central database
They can't be creating a new repository for each "version" of each diagram.

For me this is a pure "sales" feature. It looks good in a demo, but it utterly useless in the real world.

Geert

4
Automation Interface, Add-Ins and Tools / Re: Reading EA Version
« on: June 02, 2026, 09:48:37 pm »
I don't think there's a direct property in the API you can query.

So you'll have to do it with a workaround. And that workaround will be different depending on the langueage you are using.

On Stackoverflow I found something like this https://stackoverflow.com/questions/7759715/check-if-my-program-is-running-in-32-bit-mode-on-a-64bit-machine-if-running-in#:~:text=You%20can%20use%20IntPtr.,if%20running%20as%2064%20bit.
Code: [Select]
private static bool Is64BitConfiguration()
{
     return System.IntPtr.Size == 8;
}

Geert

5
Hi Richard,

I'm not convinced the transform templates are capable of correctly transforming a logical model into a relational database model.
I think there is too much, and too complex logic involved to be able to solve that with the template approach.

I wrote an add-in for a specific client to automate this transformation https://bellekens.com/ea-database-transformer/
This add-in is unlikely to be useful for anyone else, but the logic involved in transforming an LDM to a DB model is not simple.

There are a lot of complexities to think about
- flattening inheritance
- datatype transformation
- naming conventions
- converting associations into FK's (especially many-to-many associations)
- ...

Geert

6
You can override the standard labels, and define how they should look like.
I guess that is where you can also set the fontcolor etc...

Code: [Select]
label middlebottomlabel
{
      println("#NAME#");
}

Geert

7
I think the "security" feature is a bit of a misnomer.
It's more like a feature to protect users from themselves.

It's not "real" security.
If you know what you are doing you can quite easily give yourself admin rights in EA and do whatever you want.

If you give users access to your repository you should trust them to not be bad actors.
If you can't, you shouldn't give them access.

That's different for something like Prolaborate. This product is intended to be accessible from the (big bad) internet, and it should have "real" security.

Geert

8
How they show on a diagram is not specific for WebEA (or Prolaborate).
The diagram is shown as an image, and it generated by EA.

It could be that WebEA is still showing an old version of the diagram (with attributes in a different order).
You can test that by changing something else on the diagram, and saving it.
That should trigger the re-generation of the diagram image.

Geert

9
General Board / Re: How to Disable Stereotypes Globally EA 17.1
« on: May 16, 2026, 03:41:46 pm »
The easiest will be to use the template package I think.

Geert

10
General Board / Re: Property Type via Script
« on: May 12, 2026, 08:40:07 pm »
Not sure if this applies to your case as well, but for attributes there are actually two field.
One field
t_Attribute.Type is the name of the type
t_Attribute.Classifier is the ID of the datatype for this attribute.

The standard dropdown (int, string, boolean) only sets the type field. If you use Select Type, the Classifier will be filled in (as well as the type field)

Geert

12
General Board / Re: Property Type via Script
« on: May 05, 2026, 06:58:32 pm »
It is definitely possible.

The easiest way to find out what is happening exactly, is to check what EA sends to the database.

If you have an MS SQL Server, you can use SQL Profiler. Other databases likely have a similar tool.

In case you don't have a tool like that, I would start comparing before and after a change, and see what happens.
I'm pretty sure it will either be in t_object, t_xref or maybe t_objectproperties(tagged values).
Once you know where it is stored in the database, it's usually pretty easy to figure out what field in the API you need.

Geert

13
Bugs and Issues / Package.ApplyUserLock toggles in v17
« on: May 05, 2026, 06:30:12 pm »
I found a bug in version 17.1.1716

When a script call Package.ApplyUserLock twice, the package ends up unlocked.
This was not the case in version 15.

Steps to reproduce:

Execute the following script:

 dim package as EA.Package
set package = Repository.GetPackageByGuid("{004FDF92-DB9B-47b7-B5B1-2CE63056D724}")
package.ApplyUserLock
msgbox "User lock applied"
package.ApplyUserLock
msgbox "User lock applied again"

In version 15 the end state is that the package is locked.
In version 17 the end state is that the package is unlocked.

Reported

Geert

14
In general it is enough to set the direction. You shouldn't touch the Navigable properties.
Direction and navigability in EA depend on each other, and you get some weird results if you modify both.

Also the order in which you update stuff (or not) matters.

PS. I still have no clue what you are trying to achieve here.  Are you only trying to update the cardinality fields?

Geert

15
Eric, if you give a bit more information we would probably help you.

Make sure to include

- a complete enough code sample that can be used to replicate the issue
- the "start" situation
- what you are trying to achieve
- the current end result

You are saying things "aren't working" but that is not very helpful as a description of the problem.

Geert

Pages: [1] 2 3 ... 902