Author Topic: Some text fields still character encoded when displayed in result list  (Read 1069 times)

miksko

  • EA User
  • **
  • Posts: 54
  • Karma: +2/-0
    • View Profile
I have set up a model search definition, to list all the requirements contained in the selected branch. The requirements have tagged values.

Since the requirements are written in Swedish, they all contain the local letters å, ä and ö. When used in the tagged values, they are all displayed correctly in the result list. But when they appear in the general Note field, the are presented as code, like:

å instead of å
ä instead of ä

The tagged values are Short Text while the Note field is Long Text. Apart from that, there is no difference.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13387
  • Karma: +566/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
You have to tell EA they are in formatted text fields. See https://sparxsystems.com/enterprise_architect_user_guide/17.0/model_publishing/create_a_custom_sql_query.html
That works for templates, so I guess it will work for searches as well.

Geert

miksko

  • EA User
  • **
  • Posts: 54
  • Karma: +2/-0
    • View Profile
You have to tell EA they are in formatted text fields. See https://sparxsystems.com/enterprise_architect_user_guide/17.0/model_publishing/create_a_custom_sql_query.html
That works for templates, so I guess it will work for searches as well.

Thanks for your suggestion Geert but I can't make it work.
I'm running a file repository (.eap) for my experimentation. According to the documentation a query should then be set up like this:

Code: [Select]
SELECT ea_guid AS CLASSGUID, Object_Type AS CLASSTYPE, Name, Note AS [Note-Formatted]
FROM t_object
Where Object_ID=#OBJECTID#

But the SQL interpreter objects to the square brackets.
Any idea what might be wrong?

Mikael

Elpis

  • EA User
  • **
  • Posts: 47
  • Karma: +7/-0
  • Make MDA/MBSE vital.
    • View Profile
I'm running a file repository (.eap) for my experimentation.
[...]
But the SQL interpreter objects to the square brackets.

As we live in 2025 now, I would avoid using ancient .eap (MS Jet aka Access) format for any purpose. There are so many better alternatives out there (e.g. .qea), with more 'standard' SQL syntax.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8083
  • Karma: +118/-20
    • View Profile
That works for templates, so I guess it will work for searches as well.
No. Searches just use the column 'Note'. The trick is that the default behavior is not to show the Note for each item. Click on the dropdown button second from the right in the toolbar. There's an option 'View Notes' that provides 3 levels of display.