I am trying to use the “Tracker associate” value type for both tracked entity attributes and data elements in tracker capture program.
I have two questions:
When I assign “Tracker associate” value type to a **tracked entity attribute** and I select a registered tracked entity for this attribute I get the UID of the tracked entity. Is there a way to get the name of the tracked entity, instead of the UID? Is there a way to control which attribute can be displayed in the “Tracker associate” value at all? See a screenshot for more clarity.
When I set a data element in a tracker capture program to be of a value type “Tracker associate” at data entry I get that this value type is not supported. See screenshot below. Why is this so? When will this value type be available for data elements? We really need this value type to be functioning.
All my test have also been performed in the Sierra Leone demo, so I can confirm that the same issues are present there as well.
Regards,
Georgi
Georgi Chakarov, CIA | georgi@logicaloutcomes.net | +1-647-478-5634 x 104 | LogicalOutcomes c/o Centre for Social Innovation, 720 Bathurst Street, Toronto Canada M5S 2R4 | * You may unsubscribe from receiving commercial electronic messages from LogicalOutcomes by emailing *info@logicaloutcomes.net
I am trying to use the “Tracker associate” value type for both tracked entity attributes and data elements in tracker capture program.
I have two questions:
When I assign “Tracker associate” value type to a **tracked entity attribute** and I select a registered tracked entity for this attribute I get the UID of the tracked entity. Is there a way to get the name of the tracked entity, instead of the UID? Is there a way to control which attribute can be displayed in the “Tracker associate” value at all? See a screenshot for more clarity.
When I set a data element in a tracker capture program to be of a value type “Tracker associate” at data entry I get that this value type is not supported. See screenshot below. Why is this so? When will this value type be available for data elements? We really need this value type to be functioning.
All my test have also been performed in the Sierra Leone demo, so I can confirm that the same issues are present there as well.
Regards,
Georgi
Georgi Chakarov, CIA | georgi@logicaloutcomes.net | +1-647-478-5634 x 104 | LogicalOutcomes c/o Centre for Social Innovation, 720 Bathurst Street, Toronto Canada M5S 2R4 | * You may unsubscribe from receiving commercial electronic messages from LogicalOutcomes by emailing *info@logicaloutcomes.net
Thank you for your response! I will post the issue in JIRA.
Do you think that you have a way of prioritizing the Tracker associate becoming available at data element level? We are very needful of this feature. Since Tracker associate is already available at tracked entity attribute level and is functional, do you see it as a lot of effort to make it work at data element level as well?
I am trying to use the “Tracker associate” value type for both tracked entity attributes and data elements in tracker capture program.
I have two questions:
When I assign “Tracker associate” value type to a **tracked entity attribute** and I select a registered tracked entity for this attribute I get the UID of the tracked entity. Is there a way to get the name of the tracked entity, instead of the UID? Is there a way to control which attribute can be displayed in the “Tracker associate” value at all? See a screenshot for more clarity.
When I set a data element in a tracker capture program to be of a value type “Tracker associate” at data entry I get that this value type is not supported. See screenshot below. Why is this so? When will this value type be available for data elements? We really need this value type to be functioning.
All my test have also been performed in the Sierra Leone demo, so I can confirm that the same issues are present there as well.
Regards,
Georgi
Georgi Chakarov, CIA | georgi@logicaloutcomes.net | +1-647-478-5634 x 104 | LogicalOutcomes c/o Centre for Social Innovation, 720 Bathurst Street, Toronto Canada M5S 2R4 | * You may unsubscribe from receiving commercial electronic messages from LogicalOutcomes by emailing *info@logicaloutcomes.net
