A project is experiencing an issue where a newly created report cannot be seen from within the app by the offline user that just created the report. As a result, they cannot do the proper follow up, and the bigger concern is that the tasks for this person will not be created or seen either.
The form in question is set up to create a person, which this report does successfully, yet the report itself then disappeared from the user’s perspective. This report and workflow has worked thousands of times beforehand. The CHT app on the user’s device has fully synced, and the report shows as expected when logged on as the same user on a different device.
Although the report cannot be accessed using the direct app link to the report, it can be accessed directly with the db link. What could cause a report to be accessible via db URL directly, yet missing from the Reports tab? In other words, how could a report be accessible via https://{instance_url}/medic/{doc_id}, and not https://{instance_url}/#/reports/{doc_id}? Is the direct db link accessing the online version?
Any thoughts on what to investigate further would be helpful!
The report is missing something that would make it ‘scoped’ to the logged in user. Does it have an appropriate patient_id / place_uuid or similar that references contacts that the user has visibility to?
Thanks Derick for the suggestion. The report doc in question has a patient_uuid that matches a person that the user has access to. When I log in as that user on a different device I can see the report, so to me it doesn’t seem to indicate a scoping issue.
I’ve since found out that the doc was created by a different user… not the one that was trying to view it. And as it turns out, the user is now able to see the report. It’s been about a week, and I am not sure when the report became visible in the app. It still remains that there was a period where the report was visible as a doc, but not in the app, and restarting the browser at the time didn’t help.
I’ll report back if this occurs again, or we figure anything else out about it. In the meantime, thanks for the support and if you have ideas of what to try if this happens again, let us know!
