Hello. A few days ago I updated my dhis2 from version 2.39.3.1 to 2.39.6. However, I am facing a challenge when saving a record. After filling out the form in Tracker Capture, when I click on Save I get an alert “An error occurred, please check import summary”. Please see the attachment.
Hi @mdengojr
Could you try the Capture app and see if this issue persists? If it does then please share the details step by step how to reproduce it.
Thank you!
Hi @Gassim . Thanks for the feedback.
The Capture App works without any problems.
The problem is actually in Tracker Capture.
When I open Tracker Capture and fill out the form there, I then try to save the record and the button has no action and remains on the same page.
Only after much insistence is the record saved.
1 Like
Hi @mdengojr
Great to know that it’s working in the Capture app. The Tracker Capture is being replaced by the Capture app so would it be possible to continue using the Capture app instead?
Are there any specific reasons/blockers that delay this transition?
Thank you!
Yes @Gassim . Due to the number of users using the instance, the adaptation process would take some time. That’s why I insist on using Tracker Capture for now.
I tested it in Capture anyway and found the following error:
main.js?attr=zFTF51x…hNW20UGa3GEsqQ:2655
POST https://…/api/39/tracker?async=false 409 (Conflict)
fetchCallImpl @ main.js?attr=zFTF51x…hNW20UGa3GEsqQ:2655
window.fetch @ main.js?attr=zFTF51x…hNW20UGa3GEsqQ:2657
(anônimo) @ main.79d2f07b.js:2
fetch @ main.79d2f07b.js:2
executeResourceQuery @ main.79d2f07b.js:2
mutate @ main.79d2f07b.js:2
(anônimo) @ app.ae6af088.chunk.js:1
f @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
dispatch @ 6065.eb38dc71.chunk.js:2
e.next @ 6065.eb38dc71.chunk.js:2
t._next @ 6065.eb38dc71.chunk.js:2
t.next @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
s._next @ 6065.eb38dc71.chunk.js:2
t.next @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
t._execute @ 6065.eb38dc71.chunk.js:2
t.execute @ 6065.eb38dc71.chunk.js:2
t.flush @ 6065.eb38dc71.chunk.js:2
t.schedule @ 6065.eb38dc71.chunk.js:2
e.schedule @ 6065.eb38dc71.chunk.js:2
r @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
s._next @ 6065.eb38dc71.chunk.js:2
t.next @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
i @ 6065.eb38dc71.chunk.js:2
t.next @ 6065.eb38dc71.chunk.js:2
(anônimo) @ 6065.eb38dc71.chunk.js:2
(anônimo) @ app.ae6af088.chunk.js:1
onSave @ app.ae6af088.chunk.js:1
(anônimo) @ app.ae6af088.chunk.js:1
fs @ main.79d2f07b.js:2
Rl @ main.79d2f07b.js:2
t.unstable_runWithPriority @ main.79d2f07b.js:2
$i @ main.79d2f07b.js:2
Nl @ main.79d2f07b.js:2
(anônimo) @ main.79d2f07b.js:2
z @ main.79d2f07b.js:2
_.port1.onmessage @ main.79d2f07b.js:2
{“httpStatus”:“Not Found”,“httpStatusCode”:404,“status”:“ERROR”,“message”:“Key ‘Oa40r85gVp’ not found in namespace ‘trackerCaptureGridColumns’”,“errorCode”:“E1005”}
I’m encountering the same issue after updating from version 2.39.3.1 to 2.39.6. This error occurs intermittently when using Tracker Capture. I also tried using Capture, but I encountered similar error. The program worked perfectly in version 2.39.3.1. I upgraded my sandbox environment to version 2.40.4.1 to see if it would resolve the issue, but the problem persists.
Hi All
We are also facing this issue with Bangladesh’s national community HIS system and need an immediate solution. We also can’t use the ‘capture app’ right now because it requires training 25,000 users.
Need urgent support.
1 Like
Hi @Hannan
I understand your situation and would love to help. Unfortunately all the errors above are general ones and don’t help in uncovering the exact issue. It will be really great if we can reproduce this issue (using Tracker Capture app) in any of the play.dhis2.org instances? What is the version of the DHIS2 instance you are using?
When reproducing by following the step by step we are able to check the network requests, cache cleaning, sharing settings and configuration properly. If that still doesn’t help, we will need the full relevant logs from the Catalina.out (without the authentication/sensitive info).
Thanks!