You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Leading and trailing whitespace is not permitted for key values. However, it is possible to enter such whitespace, usually unintentionally, when typing search strings into selection criteria or editors for entity-typed properties. The whitespace is then used as part of the search string, returning no results. And so, users need to realise that they have typed a space before or after a search string, which is far from obvious.
To improve usability, it is proposed to automatically remove leading and trailing spaces from search strings used in entity-typed selection criteria and entity property editors when preparing a query.
Expected outcome
Improved usability.
The text was updated successfully, but these errors were encountered:
01es
changed the title
Entity centre: remove trailing and leading whitespace from entity-typed selection criteria
Entity centres and masters: remove trailing and leading whitespace from search values in autocompleters
Feb 26, 2024
… to trim just search from entity editors. Also adjusted for preparing serach criterias to separate entity editors search criteira from string search criterias.
Description
Leading and trailing whitespace is not permitted for key values. However, it is possible to enter such whitespace, usually unintentionally, when typing search strings into selection criteria or editors for entity-typed properties. The whitespace is then used as part of the search string, returning no results. And so, users need to realise that they have typed a space before or after a search string, which is far from obvious.
To improve usability, it is proposed to automatically remove leading and trailing spaces from search strings used in entity-typed selection criteria and entity property editors when preparing a query.
Expected outcome
Improved usability.
The text was updated successfully, but these errors were encountered: