Sent the Pull Request for save/update location mappings
Created issue for Updating run reports UI to work with location mappings
Tested Upgraded Run Reports UI locally
Send data function is completed
Download DXF json functionality is also completed
Download ADX functionality is not completed yet.
It throws a Class Cast Exception Request processing failed; nested exception is java.lang.ClassCastException: javax.xml.namespace.QName cannot be cast to javax.xml.namespace.QName
Need to find the reason for the error
Tested the Upgraded Automation UI with location mappings locally
The Pull request for location mapping UI was merged yesterday. Thank you @jayasanka and @akshika47 for reviewing and merging.
I found that the ADX download option (in Run Reports UI) is not working in the current version of the DHIS Connector Module. It throws a 500 Internal server error.
I created 2 new pull requests for Upgrading run reports functionality and automation functionality. Still, the Pull requests are in draft mode. I need to do recheck it before making it ready for review.
This is the automation UI that I have designed now. But I noticed that with this design, users can’t see which locations-orgunit mappings are available for the selected mapping.
In the run reports UI, it automatically shows the available location-orgUnit sets but here it doesn’t.
So do we need to show the available location-orgUnit sets in here also? Or is that not needed
Hi @jayasanka@akshika47, I was able to upgrade the Automation(Scheduling) functionality of DHIS Connector module integrating it with Automated Location Mapping, so the users don’t have to choose the locations and org. units manually. Here’s a small preview.
Unable to update data model using liquibase.xml - Module DHIS Connector
With the automated location mapping feature, the database of module will be changed a bit. Unwanted columns of both tables used in DHIS Connector Module will be removed.
This may cause an error saying Unable to update data model using liquibase.xml after updating the module. I found the solution for this issue from here
This sometimes happens with OpenMRS modules. Ideally liquibase existing changesets should never be modified and if there is a modification required, it should be added as a new and subsequent changeset.
Liquibase makes entries in table liquibasechangelog to keep track of executed changesets with a checksum/hash. When changeset is modified the checksum is found different and this error is encountered.
In above script we removed all tables created by previous version of team module, and also deleted all liquibase entries made by this module to allow module installation start from point zero. Offcourse, if it were production server, we never had deleted the tables. Also we never delete liquibase entries to avoid already executed changesets run again (this sometimes can also cause failed installations)
Deleting every row related to DHIS Connector module in the liquibasechangelog fixed the issue. Sometimes you may need to delete the report_to_dataset and location_to_orgunit table too
Hi. The user access control system is almost completed now. I sent pull requests for adding privileges to all the pages except the import/export pages. All the details and screenshots are posted in this thread: DHIS Connector Module - User Access Controlling
These are the Pull requests for adding privileges:
Added a new button to toggle automation in automation page. Users with Manage Automation and Manage Global Properties privilege can toggle automation with this button.