What's the rational behind the need to search for a the whole value of a unique TEI attribute?

Sometimes when we are searching for TEIs, we only have a part of their unique ID (e.g. the last 5 digits) and therefore need to search based on the partial information that we have.
While this is possible for non-unique attributes, it is not possible for unique attribute where we need to put the Exact value as per the screenshot bellow and as tested in the system:

What’s the rational behind this choice for searching?
And what are the implications of disabling it?
While some might consider this as feature, we consider it a bug :rofl::stuck_out_tongue_closed_eyes::innocent::hot_face:

What are your thoughts about this issue? and is there a way to solve it?

1 Like

That’s a good question; tagging the @dhis2-tracker team to shed more light on this as other members also contribute to it.



1 Like

Hi there,
When searching for an exact value this lets the app do some assumptions - for example that there will be only one or zero hits on the search. In the API, searching this value alone should always be allowed, even if “soft searching” requires at least 2 or more attributes.
Having an effective user interface for partial ID searches is a bit of a challenge, not to say that we will not try to meet the reqiurement. Its great if you can create a user story jira issue - describing the use case in short, and link it here.


1 Like