Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: miksko on April 24, 2025, 02:12:29 am
-
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.
-
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 (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
-
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 (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:
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
-
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.
-
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.