Hie, I need to know how to configure a tracker program so that a person registered in this program should be able to be enrolled into another program. Documentation says I need to have same tracked entity attributes in these two programs and I have tried but still the other program is not being listed in the program enrolment page.
What about the OUs are they assigned in both programs? If program 1 is assigned to OU A but program 2 is not then even if they share the same TEI, it’ll not be possible to enroll TEI in program 2 when the OU is A…
There might be other possible reasons so it will help if you could add screenshots, info, and hopefully steps to reproduce. Thanks!
We are working on replicating the eLMIS sandbox RTS tracker: DHIS 2
There is a need to link a registered item (in the Health Product Catalogue app) to the RTS tracker app. They are both using the same TEIs and OUs but they are standalone i.e. unable to enroll a catalogue item to the RTS tracker app.
The Tracked Entity Type in each program is different, the (Real-Time Stock Management) TE type is Item whereas the (Health care product catalogue) TE type is Health care product; therefore, it is not possible to enroll a “health care product” into RTS program because the TE type in RTS is “Item.”
If you explain the use case more, there might be a workaround but unless the Tracked Entity Type for both programs are the same, it’s not possible to enroll a TE type that the program is not dedicated for.
So, the use case is that I am trying to find a better use of the catalogue by setting up the same TE as the RTS.
Additionally, 2 scenarios I need clarification on:
I want to be able to register an item in the catalogue and then enroll it in RTS without having to create the same item in the RTS web app.
For the Use Case app to work, you create a tracker program that gets linked in the Use Case app configuration.
One of the challenges we have encountered is that, if we add a field in the normal tracker program, the Use Case app does not display it. It only shows transactions we set up in the Use Case app (which seems the default setup).
We want to enroll one person from tracker program Y to program Z. Both tracker programs use the same tracked entity with common attributes, although program Z has more attributes than program Y. We have managed to enroll person A from program Y to Z following the steps below:
The steps we followed to enroll person A from program Y to program Z:
We search for the person we want to enroll into program Z and we click on the three dots in the upper right corner and choose more enrollments
After filling the attribute fields (those which are not common) in Program Z, and click on the sync button, it display the following message box. However, clicking on the send button, the app repeatedly prompts us to send changes but does not successfully upload the data to server.
thanks for the detailed report. We would need to reproduce the issue to figure out the cause, I have just tried to replicate it with a basic configuration (demo instance) and it worked fine for me. Could you share more details about the configuration? If it were possible to have a test user in that instance, that would be great (send me a direct message if so).
Below, do you mean the test-user for android capture ( URL, test-user and password)?
Yes, I meant that. It would be the easiest way to reproduce the issue. I have tried enrolling a TEI in two different programs following the steps you mentioned and I wasn’t able to reproduce the issue, it worked fine for me.
If it is not possible to share testing credentials, please add more details about the programs, as much as you can. It is difficult to foresee what is making the sync fail: