Beekeepers Tracker Program

Implementation - Implémentation
1

Dear Community,

I’m experiencing the same issue. I’m working with two tracker programs: Beekeeper (Person TET) and Apiary (Person TET). I created a relationship type called “Beekeeper owns Apiary,” where the intended logic is:

  • One Beekeeper can own multiple Apiaries (1:N)

  • Each Apiary should only be linked to one Beekeeper

However, DHIS2 currently allows me to relate a single Apiary to multiple Beekeepers, which does not fit the required data model.

Based on my tests and what I’ve read in previous discussions, it seems DHIS2 does not currently enforce cardinality constraints on TEI relationships. Before I consider alternatives, I’d like to ask:

  • Has there been any update or new feature that supports restricting relationships to 1:N or 1:1?

  • Is there any recommended workaround or best practice (e.g., using program rules or custom validation) to ensure an Apiary cannot be linked to more than one Beekeeper?

Any guidance or recent developments would be greatly appreciated.

Thank you for your guidance!

1 Like
2

It’s always interesting to learn about a new use case. You are the first person that I know of using DHIS2 for apiary.

With regards to your question – is it likely that there will be data entry users that might link an apiary to multiple beekeepers? Before considering a software solution, it’s always a good idea to confirm the work process.

1 Like