[ LMIS Usecase ] Updating tracker attribute not working using program rule with DE values of stage

[jpatrick (Joseph Patrick)]

Hello community leaders,

Do we have any known issues in assign action in program rules for updating tracker attributes with data element values from stage? This is for an LMIS usecase

Requirement: We will receive medicine stock from donors and will enrol the details in tracker. There is one enrolment tracker attribute called Remaining Quantity. During initial enrolment it will be same as Total Quantity.

After enrolment, for each event in distribution stage Remaining Quantity tracker attribute needs to get updated like
Total Quantity - Distributed Qty

Rule is getting evaluated, but tracker attribute not getting updated, any suggestions would be extremely helpful

[jpatrick (Joseph Patrick)]

Rule action screenshot for more details

[jthomas (Jins Thomas)]

Hi @Scott probably you can guide him on this?

[jpatrick (Joseph Patrick)]

Hello @Karoline Shall i request your help on this? Can this be a bug? or i’m using it wrongly?

[Scott (Scott Russpatrick)]

Hi @jthomas this looks correct to me. What version are you using? Can you reproduce the issue on play.dhis2.org?

Tagging the tracker team if they can help more - @YuryR @Enzo and @Markus

[jpatrick (Joseph Patrick)]

Hello @Scott @YuryR @Enzo @Markus

Dhis2 version is 2.35.1

I was able to reproduce this in play.dhis2.org. May be tonight it gets overwritten?

https://play.dhis2.org/2.35.1/dhis-web-maintenance/index.html#/edit/programSection/programRule/SHoqZenelzk

[YuryR (Yury Rogachev)]

Hi @jpatrick !

I can confirm that the value does not get assigned to the attribute as a result of the programRuleAction in your Program Rule.

However, I cannot confirm that it is impossible to assign values to attributes.

I have tested by creating a simple PR (it is still in play):

https://play.dhis2.org/2.35.1/dhis-web-maintenance/index.html#/edit/programSection/programRule/mOnuow34bjo

It is set up to always assign a value to the attribute and the value is assigned, but only when the program stage is not specified in the program rule.
If the program Stage is specified, the value does not get assigned to the attribute.

This leads me to a conclusion that the assignment of a value to an attribute can only happen during enrollment.

[jpatrick (Joseph Patrick)]

Hello @YuryR

Thanks for helping me on this. Yes during enrollment it worked for me too.

So is it a feature limitation or design that we cannot update attribute values during stages?

How can i confirm this. If it’s a limitation what could be the best alternate workaround to make it happen.

I would like to seek your kind advice

[jthomas (Jins Thomas)]

That’s strange, Should we raise a JIRA if it’s a bug @YuryR It looks to be a nice to have feature in LMIS

[Karoline (Karoline Tufte Lien)]

So at the moment, you cannot change or assign TEA data values with program rules when you enter data in program stages.

Here is some further information on that:

Assign value to a tracked entity attribute with an option set

Ok, that makes it a bit more tricky. You probably want to assign and save tracked entity instance attributes while filling in data in an event. The problem with this is that the assignments to tracked entity attributes will be triggered when you are in the registration form, or if you open the edit profile widget - but generally not when you enter data in program stages. There has been a few requests to allow assigning TEI attributes from everywhere in the program, and we can conceivably suppor…

Webinar on Tracker Implementation Considerations, Wednesday 28 April - Q&A thread - Add your questions and comments below

Hi Mahmud Unfortunately there is no way to immediately ASSIGN a value to an TEI Attribute while you are updating a program stage. You would need to again open the registration form with the TEI Attributes. This is by design: here is an explanation from Markus Of course there may be workarounds with custom scripts etc to update the TEI attribute via a PUT request, depending on the use case, but there is no built-in solution. Perhaps you could consider a warning box in the program stage to ask…

“The problem with this is that the assignments to tracked entity attributes will be triggered when you are in the registration form, or if you open the edit profile widget - but generally not when you enter data in program stages.”

I have talked to the devs and since this is a feature, not a bug, I have created the following issue: [DHIS2-11025] - Jira - follow that issue for updates.