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 - Guillaume

Pages: [1] 2 3 ... 42
Suggestions and Requests / Quick access toolbar
« on: June 20, 2018, 06:45:27 pm »
Since ribbons are available in EA, it would be useful to have a Quick access toolbar as with Word, Excel, Powerpoint...

Suggestions and Requests / Re: Package Indicator for Baselines
« on: June 20, 2018, 04:26:06 pm »
+1 with a new option to enable/disable this icon (it can be relevant to hide it so users don't ask questions on what this is - remember the bookmarks red icon, or the linked document 'A' icon)

Suggestions and Requests / Re: Import ODATA (EDM)
« on: June 20, 2018, 04:23:22 pm »
As an update on this one, I identified as a potential solution using XSLT to generate a CSV that will let me import Classes and Attributes into EA.

Suggestions and Requests / Import ODATA (EDM)
« on: June 18, 2018, 05:11:33 pm »

I have a request to import ODATA metadata information in EA.
This is a standard and an example is available here:$metadata

I managed to import the EDM XSD in EA ( and

I tried to change the metadata XML file so it looks like an XSD, with a reference to the EDM XML schema, e.g. by adding the following (see content from the link above)

Code: [Select]
<?xml version="1.0" encoding="utf-8"?>
<Schema Namespace="odatatest" xmlns="">
      <EnumType Name="PersonGender">
        <Member Name="Male" Value="0"/>
        <Member Name="Female" Value="1"/>
        <Member Name="Unknown" Value="2"/>

Running the XSD import in EA doesn't generate anything, even when I enable the Import Ref XML Schema option.
I feel I'm not far from getting the expected result. Any idea?


The view height was indeed too small to see the list of parameters. It's a tricky UI design issue as moving the list at the top mayh make it difficult to update the parameters details..


Using EA14 Build 1420, I'm working with class operations. The Features&Properties view works fine to create new operations, but the Operations Properties doesn't let me enter anything.
I double click on the Parameters cell of an operation in Features&Properties -> Operation Properties opens up. Then all the fields are greyed out/disabled.

I also found an issue in using Image Assets: pressing F2 doesn't let me rename the element.

Suggestions and Requests / Re: Auto Name Counters shared by 2 Types
« on: May 31, 2018, 12:32:59 am »

As a workaround you can define all your elements first, then place them on a diagram (in the order from top to bottom or left to right), and use eaUtils Generate Alias feature.
More info available from

Hope it helps.

Bugs and Issues / EA14 Special action / Properties dialog
« on: May 24, 2018, 08:46:46 pm »
When I right click on a class from a diagram to open the properties popup, I need to go to Properties > Special action...
Looking at the DESIGN ribbon > Element > Properties, the matching command is called Properties Dialog which makes sense.

It would be best to rename this Special Action with Properties Dialog.

Bugs and Issues / Re: EA 14 Import DB fails
« on: May 24, 2018, 08:44:02 pm »
I ran it on an ODBC DSN for a Postgres DB.

Bugs and Issues / EA 14 Import DB fails
« on: May 24, 2018, 06:26:58 pm »

I try to run an Import DB Schema in EA from an existing DB via an ODBC data source.
Once the Import starts, I get an 'Error retrieving table list' message when using EA 14 build 1420.

Running the same test in EA13.5 works fine.

General Board / Re: Step by step Guide
« on: May 18, 2018, 04:24:36 pm »
Hi Pierre,

For requirements gathering, it is very common to create a model with separate branches (packages in EA) for Functional and Non-Functional requirements (see FURPS for an example of requirements classification). Requirements can be updated in EA and/or via Excel export/import. It is also important to think about traceability with your other modelling artefacts.

With EA, you have all types of diagrams you need incl Requirements, but you always need to define a suitable Model structure. Good examples are shared by the users community or also provided by Sparx in the EA Example (with EA 13, open START > Help > Open the Example Model. In the project open Analysis and Business Modeling > Requirements Model). This is very often where Sparx partners come into action with advice & training services.
For some specific needs, requirements can be tailored with stereotypes (UML profile) e.g. to add additional fields such as RefID, Category, etc.

I don't use Project Management features as dedicated tools like JIRA and others are more suitable (EA is a very open tool making it possible to integrate with other tools).

For test cases, it can be used but again based on your need.

Please note about the upcoming EA users gathering on the 8th of June in London where you can follow useful presentations and meet experienced EA users and experts:


I submitted  a feature request for a new method to refresh the script tree.


I found an easier option (in my opinion) by calling a function at the beginning of each script that copies its content/code to a dedicated "Run Last" script (with separate versions for the Project Browser and Diagram).

It works yet I can't find a way round an annoying issue: the screen tree list must be refreshed by the user (or the project closed/opened) so the updates are taken into account (see my related post here:,39778.0.html).


I have a script that carries updates in the scripts list. To see the changes, I have to click on the Refresh Script Tree button (Scripting view) or restart the project.
Is there a way to run this via the API, perhaps with the undocumented Repository.CustomCommand  method?


Hi Nizam,

Thanks for the links.

Pages: [1] 2 3 ... 42