LarsI have finally solved the puzzle...I suspect that the person
importing these org units misaligned the formatting because the uids were
actually loaded in the org unit name column and what I thought were the
uids were actually the "org unit names". I should have picked that up
straight away
Thanks Lars or your response.
Yes I did clear cache statistics as well as browser cache. How does the
application determine orphaned organisationunits? Organisationunits without
a parentid? Or a parentid that does not exist?
Regards
Ant
On 16 August 2015 at 07:20, Lars Helge Øverland wrote:
>
Hi Ant,
after doing SQL against a running DHIS 2 instance you might want to go to
data admin > cache statistics > clear cache. This since the cache might
become stale unknowingly as a result of direct SQL queries.
regards,
Lars
On Sat, Aug 15, 2015 at 12:05 PM, Ant Snyman wrote:
> Dear All,
Hi Sumudu,
yes there are two options:
1. You can go to the data items > data elements section, the for data
elements you select "Details" instead of "Totals"
[image: Inline image 1]
2. You can make sure your category is marked as a "Data dimension" in the
maintenance (make sure to re-run analy
Dear All,
DHIS2 vesrion 2.20 snapshot, build 19527
The data integrity checks showed some "orphaned" org units which should not
have been on the system.
So I wrote scripts to clean out the org units and checked all 37 tables
that either reference organisationunitid or sourceid and cleaned out all
5 matches
Mail list logo
