Messages

1

Automation Interface, Add-Ins and Tools / Re: Save Package as MDG Technology .... Question as to how to create a custom id

« on: February 27, 2025, 04:44:40 am »

Yes. I tried that and also tried adding a tagged value named Id to see if that would work. But no joy.

Doing it the old-fashioned way is tedious when you have this new slick way. It requires

Ultimately, I cheated and edited the XML file to change the Id. But it seems weird that I can import the package as an MDG with no issue. Seems inconsistent.

2

Automation Interface, Add-Ins and Tools / Save Package as MDG Technology .... Question as to how to create a custom id

« on: February 26, 2025, 08:54:58 am »

I am trying out building my own MDG Technology in EA 17 and I love the Save Package as MDG Technology, in concept. I started with one of the TEA accelerators and did a few tweaks. I can load it fine using the "Import Package as MDG Technology" option from the Publish Technology action on Specialize ribbon. It works fine. Now I exported the technology using the "Save Package as MDG Technology" option and got an XML file.

When I go to import the technology, I get a message saying that this version of EA only supports an ID of 12 characters or less. When I look at the technology file, it uses the package name as the ID and the name for the technology. My question would be is there a way for me to provide a shorter ID as meta data that will be used when saving the package as a technology file? I checked the documentation, but this seems not to be covered at all. Lots of info on the manual way of exporting profiles and creating an MDG.

I know I can cheat and shorten the package name but it would be nice to keep the descriptive name for the technology and have a shorter id value.

I opened the XML file and manually changed the ID and was able to import successfully but would prefer not to have to do this manually each time. Is there an undocumented feature that I can add a piece of meta data to the MDG package to indicate the ID. I tried using the alias field, but that did nothing.

Any solutions would be appreciated.

3

General Board / Re: Save Package as MDG Technology .... Question as to how to create a custom id

« on: February 26, 2025, 08:42:08 am »

I cheated and edited the XML file and it loaded fine. I just shortened the ID to make it acceptable. But, would be nice not to have to make that change manually each time.

4

General Board / Save Package as MDG Technology .... Question as to how to create a custom id

« on: February 26, 2025, 08:34:10 am »

I am trying out building my own MDG Technology in EA 17 and I love the Save Package as MDG Technology, in concept. I started with one of the TEA accelerators and did a few tweaks. I can load it fine using the "Import Package as MDG Technology" option from the Publish Technology action on Specialize ribbon. It works fine. Now I exported the technology using the "Save Package as MDG Technology" option and got an XML file.

When I go to import the technology, I get a message saying that this version of EA only supports an ID of 12 characters or less. When I look at the technology file, it uses the package name as the ID and the name for the technology. My question would be is there a way for me to provide a shorter ID as meta data that will be used when saving the package as a technology file? I checked the documentation, but this seems not to be covered at all. Lots of info on the manual way of exporting profiles and creating an MDG.

I know I can cheat and shorten the package name but would be nice to keep the descriptive name for the technology and have a shorter id value.

Any solutions would be appreciated.

5

Bugs and Issues / Re: Crash on Manage Libraries

« on: May 03, 2024, 04:32:33 am »

I too had this issue with 16.1 Build 1628 64 bit version

6

Automation Interface, Add-Ins and Tools / Re: Setting direction on connectors

« on: March 29, 2024, 08:27:42 am »

Have tried both ways. But, no joy. The aggregation property is set properly. At this point, I am left with manually selecting and changing the direction of each link.

7

Automation Interface, Add-Ins and Tools / Setting direction on connectors

« on: March 06, 2024, 10:54:54 am »

I have written a simple script that creates composition links between an element and any child elements. It works except that when I try to set the direction, I don't get the effect for which I am looking to achieve. I want "Source -> Destination". But it always sets it to "Destination -> Source". I

         var theElement as EA.Element;
         theElement = Repository.GetTreeSelectedObject();
         
         elements = new Enumerator(theElement.Elements);
         while (!elements.atEnd()) {
            var element as EA.Element;
            element = elements.item();
            connector = element.Connectors.AddNew("Part Of","composedOf");
            connector.SupplierId = theElement.ElementID;
            connector.Direction = "Source -> Destination";
                                 // Assuming need update here so that the supplier end is filled in properly.
            connector. Update();
                                // this works fine. Aggregation is showing properly.
            connector.SupplierEnd.Aggregation = 2;
            connector.Update();
            elements.moveNext();
         }

8

Suggestions and Requests / Re: MDG generation automation

« on: March 17, 2016, 06:35:23 am »

Has this ever been addressed? I am finding same issue. Easy to write a script, but need a way to call the function that assembles the profile. It would make updating / maintaining MDG's much easier.