After upgrading from 2.21 to 2.25 we have found the following error:
Code: 500
Status: Internal Server Error
Not a valid dimension: BtFXTpKRl6n
This uid, BtFXTpKRl6n, is an organisationUnitGroupSet that, in the Layout of a graph/table, is placed in the filter section.
The tricky thing is that the behaviour is not always the same. Sometimes we can open those tables and graphs and sometimes not. In particular once we get the error, if we perform the Maintenance Task Clear application cache, it works again. But suddenly, after some time, we start getting the same error again in the same table/graph or in others with the only thing in common that they have this organisationUnitGroupSet as a filter.
We are looking into it right now but if any of you have faced a similar problem or have an idea on what it could be, thank you for sharing!
We found out that the error was due to some organisationUnitGroups being part of more than one organisationUnitGroupSet. In those cases, if you list the organisationUnitGroups with an API call you get multiples instances for those organisationUnitGroups (one per orgUnitGroupSet they belong to). And in the end, this is the cause of inconsistencies with standard DHIS2 modules such as the one described above. We solved it by duplicating the orgUnitGroups so they belong only to one orgUnitGroupSet.
This happened to us before with categoryOptionGroups and categoryOptionGroupSets and we solved it in the same way. But it took us some time to match both issues.
Just in case you face the same issue!
One question, is this the expected behaviour?
Cheers!
Alejandro
ยทยทยท
On Thu, Jan 26, 2017 at 10:01 AM, Alejandro acasrod@gmail.com wrote:
Hi all!
After upgrading from 2.21 to 2.25 we have found the following error:
Code: 500
Status: Internal Server Error
Not a valid dimension: BtFXTpKRl6n
This uid, BtFXTpKRl6n, is an organisationUnitGroupSet that, in the Layout of a graph/table, is placed in the filter section.
The tricky thing is that the behaviour is not always the same. Sometimes we can open those tables and graphs and sometimes not. In particular once we get the error, if we perform the Maintenance Task Clear application cache, it works again. But suddenly, after some time, we start getting the same error again in the same table/graph or in others with the only thing in common that they have this organisationUnitGroupSet as a filter.
We are looking into it right now but if any of you have faced a similar problem or have an idea on what it could be, thank you for sharing!