Cannot see TEI relationship created on DHIS2 Tracker (Mobile App) on Tracker Capture (Web)

Support - Assistance technique
,
1

Hello.

I’m having an issue with creating relationships on the Tracker mobile app. I created a relationship between two tracked entities on the mobile app. I can see the relationship on the mobile app but the relationship didn’t appear on the Tracker Capture app on Web after syncing.

The weird thing is relationships created on the Web app appear on the mobile app after syncing. Has anyone experienced this bug?

Thanks in advance!

2

Hi Clara,

It’s very important to know if this is actually because of the configuration/network connection or an actual bug. It would be a bug if it’s reproducible in any of the play.dhis2.org instances! (login with android / Android123)

Are you sure that the sync was successful? In your instance, what is the type of relationship you are creating? Bidirectional?

Would you please double check if the relationship appears in any of the TEI dashboards (in the Relationship widget)? I’d also recommend checking the API [yourInstanceURL]/api/trackedEntityInstances/[trackedEntityInstanceID].json?program=[programID]&fields=relationships
You can find the ids in the address bar when you go to the TEI dashboard - see image:

Address Bar shows IDs
Address Bar shows IDs3004×926 157 KB

Also, please check if there are any errors in the console (F12) when you open the dashboard!

Thanks!

1 Like
3

Hi Clara,

in case you are using Android Capture app 2.5.0 and the relationship is unidirectional, you might be impacted by this bug ([ANDROSDK-1473] - Jira). If so, I would recommend to upgrade to version 2.5.1, which was released yesterday.

3 Likes
4

Thanks @vgarciabnz! You were right! It worked when I updated my app. Thank you!

1 Like
5

We are having this same issue. Our users are creating relationships using an android device, but are unable to see in the web environment after syncing.
This is happening with different users in different parts of the world. I am thinking it may be a bug because we cannot figure out what is causing this error.
@Gassim have you heard of anyone having this issue lately. We are seeing it with App version v2.9.1

6

I see this post is old, so I am wondering if the issue has returned