When I click one of the categories in the Maintenance app, I got the error
Can not add a Model without id to a ModelCollection and a blank page.
I fetched the category in with the api and find out that the categoryCombo payload on it appears like
"id": "sdfg6yhji8" reference a deleted categoryCombo. So I go to the database and manually deleted it. When I fetch the data with api again, it’s now appearing like:
When I inspect the Network tab to see what what fetched to the Maintenance app, I got the screenshot below which correspond with the api request.
My question is how do I delete the null value. I have clear the server cache, site cache, reload app but no changes.
I think for this one you need to check the database directly. I searched for the error “Can not add a Model without id to a ModelCollection” and that’s the conclusion…
Before I posted, I also search for existing solution but couldn’t get one. Also I have inspected the database and query the categoryCombo and categoryOptionCombo even with the condition where COC is null nothing was return. I updated the record with the Maintenance App still it is sending the null value.
So far, I have leave it for now but I can edit the categoryCombo. I only hope at some point the system will purge it.
I am experiencing this same issue and have completed the same troubleshooting tasks with no apparent resolution available. 184.108.40.206
I only escaped this when I spin up a new instance. I was unable to fix it.
I’m encountering in the same problem on the same version.
This is the issue here: [DHIS2-15351] - Jira which will be included in the next official release of each branch. We have tested and verified on the development branch of 2.39.3
Still no resolution to fixing this issue. Today, this link doesn’t work and gives us the error:
Can not add a Model without id to a ModelCollection
which redirects to:
@Gassim can you remove the [fixed] tag from the title as the issue is not wholly resolved?
Thank you for the notice. It did get fixed for version 2.39 but it wasn’t reported for version 40 but I don’t know if it was already working in version 40 and this bug reappeared?
Yes, same issue that is described in the ticket linked to this topic. Thanks!
As you can see the comment by @viet in the Jira issue, the issue is fixed in version 40.1.0 which is the latest stable version for version 40; so it should be available as soon as you update.