Just needed to know if anyone is getting the same error from the Line Listing app.
Error log below:
Click here to view error log
Error: There is no option with the value: “0”. Make sure that the value passed to the selected prop matches the value of an existing option.
Error: There is no option with the value: “0”. Make sure that the value passed to the selected prop matches the value of an existing option.
at vc (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:289443)
at Ki (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:767417)
at ks (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:813523)
at yl (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:806283)
at gl (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:806208)
at sl (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:803217)
at URL/apps/line-listing/static/js/138.36666cc1.chunk.js:2:754695
at t.unstable_runWithPriority (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:829920)
at Yr (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:754404)
at $r (URL/api/apps/line-listing/static/js/138.36666cc1.chunk.js:2:754640)
in vc
in div
in div
in bc
in div
in div
in Kl
in div
in ec
in div
in div
in xc
in div
in _c
in div
in Tc
in div
in td
in TableDataCell
in DataTableCell
in tr
in TableRow
in DataTableRow
in tfoot
in TableFoot
in table
in Table
in div
in TableScrollBox
in DataTable
in div
in div
in js
in div
in div
in Unknown
in Xr
in div
in div
in Jd
in d
in d
in Unknown
in Suspense
in we
in div
in div
in ze
in ve
in c
in B
in ae
in V
in DHIS2RuntimeProvider
in Ie
in we
in Le
in h
To be honest this is the first time this error has been reported. I think we need to investigate this further please!
Some basic steps that might help us know the root of the issue:
First, start by clearing the cache (Browser Cache Cleaner app + browser’s ‘Empty Cache and Hard reload’). Second, please check related authorities and sharing settings. Third, try the maintenance tasks in the Data Administration app such as clearing app cache, reloading apps, analytics tables export…etc Finally, reproduce the error in your instance and share the Catalina.out log (without the sensitive info) please so that we could get more info about the error.
Hello, @Gassim@khatman I am getting exactly the same error with exactly the same error codes. I am running 2.38.1. No matter the number of elements you select and the input (event or enrollment), you get the same error.
Dear @Gassim,
Please find attached the logs as requested.
The error is not reproducible on the play instance for 2.38.1 but here are my observations.
In addition to the error from the linelisting app, the line list component of the event reports app no longer works. However, the pivot table component still works.
I have uninstalled the linelisting app and reinstalled the WAR file for 2.38.1 but the issue still persists.
I think that whatever is preventing the lineslisting app from working has also disabled that component of the event reports app and this poses a huge challenge for us right now and puts us in a big fix because of our dependence on the event reports app.
Kindly bring to the attention of those who can provide a quick solution for us.
Please remember you can add your votes to the issues for prioritization as well as watch the issue for notifications. I’ve added a link in the comments section of the issue to this discussion topic for more info, and I’ve also asked @dhis2-analytics team for review and follow up.
If anyone has a temporary workaround please feel free to share. Thank you!
Hi. Big thanks to @edoardo and @maikel for investigating this and coming up with a temporary fix.
Go to system settings → General and change the “maximum number of analytics records” from unlimited to another value. I have attached a gif. Hopefully you do not need to return > 1,000,000 records in your query for now. They will look into a long term fix but at least you can use event analytics in your instances for now.
Yes this issue affected all event analytics from my testing. So event layer maps in specific configurations are also affected (any event layer maps that use the style function for example). The solution should be a temporary fix across the spectrum of issues for now.
