fix: /events?dataElementIdScheme!=UID for shared data elements DHIS2-14968

[teleivo]

added in #19153

The issue was that if two events like blZxytttTqq and ehxNi0D67uQ in the SL DB have dataValues for the same data element only one of the events would be exported with that dataValue/element.

Example DB eventdatavalues JSONB column for blZxytttTqq and ehxNi0D67uQ

{
  "D7m8vpzxHDJ": {
    "value": "P+"
  },
  "HmkXnHJxcD1": {
    "value": "Relapse"
  }
}

{
  "D7m8vpzxHDJ": {
    "value": "PE"
  },
  "HmkXnHJxcD1": {
    "value": "Relapse"
  }
}

I made the mistake of assuming I can aggregate event dataValues like we do notes in the ResultSetExtractor of the JdbcEventStore.

dhis2-core/dhis-2/dhis-services/dhis-service-tracker/src/main/java/org/hisp/dhis/tracker/export/event/JdbcEventStore.java

Line 290 in 34c2cff

Set<String> notes = new HashSet<>();

That works for notes as they are kept in the set using their note uids which are unique across events. For dataValues/Elements we obviously need a Set scoped per event as multiple events can have a value for the same data element 🤦🏻 .

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud