dhis2: Update tracked entities endpoints to V42

[hunterachieng]

Summary

Update tracked entities endpoints to the new v42.

Fixes #754

Details

Updates create, update, upsert and destroy so that resources are mapped to the new tracker endpoints.

HTTP helpers are not affected.

AI Usage

Please disclose how you've used AI in this work (it's cool, we just want to know!):

• Code generation (copilot but not intellisense)
• Learning or fact checking
• Strategy / design
• Optimisation / refactoring
• Translation / spellchecking / doc gen
• Other
• I have not used AI

You can read more details in our Responsible AI Policy

Review Checklist

Before merging, the reviewer should check the following items:

• Does the PR do what it claims to do?
• If this is a new adaptor, added the adaptor on marketing website ?
• Are there any unit tests?
• Is there a changeset associated with this PR? Should there be? Note that
  dev only changes don't need a changeset.
• Have you ticked a box under AI Usage?

[josephjclark]

This changeset needs updating. Is this the old changeset from the last fixes?

Anyway this needs to be a major update

[josephjclark]

If this changelog doesn't apply it needs to be removed, because it'll create an inaccurate release note and confuse users

[josephjclark]

If this changelog doesn't apply it needs to be removed, because it'll create an inaccurate release note and confuse users

[josephjclark]

I think we're about there @hunterachieng. Sorry this is late, and I won't be able to get to it now until Wednesday.

I'm a bit worried about some of the docs. Big docs changes are out of scope for this work but I also think there are some innaccuracies.

Unless anyone else volunteers before Wednesday, I'll do a light sweep of the docs, do a final check, and we can release.

[josephjclark]

I think version 36+ is OK?

The new tracker API, which we use for eg create, was introduced in v36. So it should work with anything from 36+.

Also, please remove the trailing fullstop at the end of the URL. It's unnecessary and will break the URL if someone accidentally copies it into the address bar

[josephjclark]

@hunterachieng have you called the actual DHIS2 sandbox with the new APIs, or have you only tested against unit tests?

[hunterachieng]

@hunterachieng have you called the actual DHIS2 sandbox with the new APIs, or have you only tested against unit tests?

@josephjclark Yes I did

[josephjclark]

@hunterachieng the PR body is very out of date with the changes here, which is a big problem for audit trails and working in the open.

I'm going to start getting more strict about this - it's super important that PRs actually do what they say they do when they are merged.

I've updated the description to be more accurate.

[josephjclark]

TODO: remove all support for trackedEntityInstances - ie, we should NOT map it to the new tracker, and we should have examples or unit tests which use this key.

This is because the datastructure for an entity on the new tracker is different to the datastructure to the old one. It's not worth pretending to maintain support.

[josephjclark]

TODO: nestArray does NOT nest new tracker objects into the right format. In the create etc we need to ensure the data is in an array. Use util.ensureArray

[josephjclark]

TODO: on the new tracker, we need to pass async: false so that the operation completes synchronously and returns data to us.

TODO: raise an issue to later support async: true as an option. This is kind of a big deal because we need to poll the endpoints and then return data. We need to make this seamless so that we just return the completed data to the job code.

[mtuchi]

Hiya @josephjclark, please give this another round

• I have updated the tracker API implementation
• Added dhis2 Add support for async: true for Tracker API #836