Book a Demo

Author Topic: MTS file: MDG.Selections "model" attribute  (Read 3009 times)

Uffe

  • EA Practitioner
  • ***
  • Posts: 1859
  • Karma: +133/-14
  • Flutes: 1; Clarinets: 1; Saxes: 5 and counting
    • View Profile
MTS file: MDG.Selections "model" attribute
« on: August 07, 2020, 06:07:04 pm »
Hello,


When building MDG Technologies, you can store your selections for a technology in the form of an MTS file. This is a prolog-less XML file, with a single root element MDG.Selections.

MDG.Selections has an attribute model, which appears to contain the name of the proojeeect....?
Except projects don't have names.

In my case I'm working against a DBMS repository, opened through a shortcut .EAP, and the model attribute contains the base file name of the shortcut.
Not sure what it would hold if I had connected through ODBC.

Anyway, there's nothing stopping me from accessing the same MTS file in a completely different project and using it there, and failing miserably in the attempt if the file should happen to refer to any in-project content like document templates as opposed to file content such as profiles. And by "failing" I mean "omitting all content listed in the MTS file that can't be found in the project without the slightest hint of warning, and then overwriting the MTS file like as not."

The attribute value is not shown anywhere in the technology creation wizard either.

So I guess the question is, if no one ever sees it, and it isn't used for any error or consistency checks -- what is this attribute for?

Anyone?


/Uffe
My theories are always correct, just apply them to the right reality.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: MTS file: MDG.Selections "model" attribute
« Reply #1 on: August 07, 2020, 06:56:32 pm »
I've seen EA complain when using an MTS file that was generated in a different model.
I got a warning like "Look out, this mts was created on a different model. Are you sure you want to continue?"

Not sure why it wouldn't complain in your case (maybe it's version related. I think I saw this on version 15)

I tend to keep mts files in a version control system so I can easily compare them after making a change.
This has saved my ass a couple of times because suddenly certain stuff wasn't in the mts anymore.
Searches are most commonly missing, especially when there are multiple people generating MDG's.

Geert