Dhis 2 data quality app organization selection not highlighted

Support - Assistance technique
1

hello,
I am running DHIS 2.38.2.1 on the local machine and it is installed and running perfectly when accessing the Data Quality app it works but when I select an organization from the organization hierarchy tree the selected Organization will not highlight it for both Validation Rule Analysis and Follow-Up Analysis but for Outlier Detection, it works. Can you help me how to fix this

Best regards

2

Hello @Beruck

Thank you for sharing this challenge in the community! I couldn’t find a similar post to this issue.

Please check that the organization unit is assigned to the user. Does this happen to all users including superuser account? Are you able to view visualizations of this app in the Dashboard app?

Would you help debug the issue by opening the Network tab in the browser DevTools (F12 → Network) and then check either the Validation Rule Analysis page or the Follow-up Analysis page? If there are any errors that appear in the console or network tab please take a screenshot.

image
image1523×900 63 KB

Thank you!

3

Hello @Gassim ,
Please find the lock at the error log

Data Quality follow up
Data Quality follow up1143×659 78.4 KB

when i click on the org tree, the following log displayed on Console

VM194 react_devtools_backend.js:4012 The query should be static, don’t create it within the render loop!

	overrideMethod	@	VM194 react_devtools_backend.js:4012
(anonymous)	@	useStaticInput.js:10
ls	@	react-dom.production.min.js:211
kl	@	react-dom.production.min.js:257
t.unstable_runWithPriority	@	scheduler.production.min.js:19
Ba	@	react-dom.production.min.js:122
El	@	react-dom.production.min.js:257
(anonymous)	@	react-dom.production.min.js:256
q	@	scheduler.production.min.js:17
E.port1.onmessage	@	scheduler.production.min.js:14

and

VM194 react_devtools_backend.js:4012 @TODO: Why does this component unmount after a force reload?

overrideMethod	@	VM194 react_devtools_backend.js:4012
(anonymous)	@	organisation-unit-tree.js:56
ss	@	react-dom.production.min.js:211
kl	@	react-dom.production.min.js:257
t.unstable_runWithPriority	@	scheduler.production.min.js:19
Ba	@	react-dom.production.min.js:122
El	@	react-dom.production.min.js:257
sl	@	react-dom.production.min.js:239
(anonymous)	@	react-dom.production.min.js:123
t.unstable_runWithPriority	@	scheduler.production.min.js:19
Ba	@	react-dom.production.min.js:122
Ga	@	react-dom.production.min.js:123
Ka	@	react-dom.production.min.js:122
nl	@	react-dom.production.min.js:230
enqueueSetState	@	react-dom.production.min.js:132
x.setState	@	react.production.min.js:12
(anonymous)	@	profile.js:19
4

hi @Gassim,

Have you made a breakthrough here ? We’re experiencing an error similar to the one Beruck described while we’re attempting to pull the same reports.

Please advise.

Thank you!

1 Like
5

Hi @potlaki

Thanks for the question! I’m not sure I can reproduce the issue. It will help if you’d share the steps to reproduce the issue on any of the play.dhis2.org instances please.

Thanks!