Author Topic: Readable, unchangeable keys for Elements (Read 5233 times)

Michel777 · « **on:** July 20, 2013, 05:41:50 pm »

Hi,

we are going to open (for editing) our model for a wider audience, threfore we need readable, unchangeable keys for Elements.

The Element Key (GUID) is not readable (32 character long) and the short description is changeable.

E.g. the Microsoft Team Foundation Server uses model-wide , unchangeable keys (Integers 1,2,3,....) for all its elements...

Is there any solution ?

Thanks in advance,

Michel

qwerty · « **Reply #1 on:** July 20, 2013, 09:47:27 pm »

What makes you think that the GUID is not readable?

q.

Michel777 · « **Reply #2 on:** July 20, 2013, 09:59:48 pm »

We refer the requiremenst in discussion, in documents. It means it is not readable for People.

E.g. Jim, look the Requirement "{779CC4D5-59C6-4721-80B1D15DE406B0C}"

qwerty · « **Reply #3 on:** July 20, 2013, 11:52:15 pm »

Well, not completely true. You can write a simple query that finds by GUID.

Here's a way to easily do it via addin (searches the paste buffer and opens the element): http://community.sparxsystems.com/community-resources/485-57create-a-hyperlink-for-ea-elements

q.

KP · « **Reply #4 on:** July 22, 2013, 09:10:54 am »

If you go Settings > Auto Names and Counters, you can set an auto-counter on the Alias field of elements. (Only useful if you aren't already using the Alias for something else)

qwerty · « **Reply #5 on:** July 22, 2013, 10:33:41 am »

But the Alias can be changed by anyone. So it's not really save as a reference.

q.

Stefan Bolleininger · « **Reply #6 on:** July 22, 2013, 05:37:30 pm »

But you can build an addin, which prevents the Alias from changing

However, it would be great if the Alias could be switched to "Unchangeable". The Referencing with GUID oder Object_ID is not so easy.

Alias would be (in my opionion) better

Ian Mitchell · « **Reply #7 on:** July 23, 2013, 08:29:52 pm »

I agree - I get asked all the time for a human-readable, read-only, auto-generated key for elements.
An Alias attribute which is flagged as 'read only' would be perfect!

Stefan Bolleininger · « **Reply #8 on:** July 24, 2013, 04:07:27 pm »

Unfortunately it is not possible to manipulate the dialogs.

It would be a really great advantage to hide/lock some fields.

Geert Bellekens · « **Reply #9 on:** July 29, 2013, 04:15:32 pm »

We had a similar requirement (for the translation of our GUI elements) which we solved entirely on the database level.
We have a small sql script that runs at night and assigns an (integer) ID to each GUI element and stores that ID in the alias field.
And to protect it from being changed we have a trigger in the database on the updates of t_object.

I know it's kind of dirty and all, but it has been working for years now without any issues.

Geert

Sparx Systems Forum

News: