[FINERACT-1306] Reporting meta-data entry not found - All reports modules

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5.0
• Fix Version/s: 1.5.0
• Component/s: Reports
• Assignee: Michael Vorburger
• Reporter: Francis Guchie
• Created: 27/Jan/21 09:37
• Updated: 28/May/22 10:39
• Resolved: 14/Mar/21 15:56

Description

https://ipaddress/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund&genericResultSet=false&parameterType=true

One gets the response payload below 

{
"developerMessage": "The requested resource is not available.",
"httpStatusCode": "404",
"defaultUserMessage": "The requested resource is not available.",
"userMessageGlobalisationCode": "error.msg.resource.not.found",
"errors": [
{
"developerMessage": "Reporting meta-data entry not found.",
"defaultUserMessage": "Reporting meta-data entry not found.",
"userMessageGlobalisationCode": "error.msg.report.name.not.found",
"parameterName": "id",
"value": null,
"args": [

{ "value": "Report Name: reportCategoryList" }

]
}
]
}

Issue Links

• Blocked: FINERACT-1305 Release Apache Fineract v1.5.0
• incorporates: FINERACT-969 Run OWASP zaproxy.org against Fineract (e.g. fineract.dev)
• is fixed by: FINERACT-1345 Fix runreports
• links to: GitHub Pull Request #1620
• links to: GitHub Pull Request #1663