You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Rahul Pawar (Jira)" <ji...@apache.org> on 2021/02/09 13:14:00 UTC
[jira] [Comment Edited] (FINERACT-1306) Reporting meta-data entry
not found - All reports modules
[ https://issues.apache.org/jira/browse/FINERACT-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17281782#comment-17281782 ]
Rahul Pawar edited comment on FINERACT-1306 at 2/9/21, 1:13 PM:
----------------------------------------------------------------
[~vorburger] Yes, this commit was throwing the exception for:
1. reportCategoryList.not.found (for: [https://localhost:8443|https://localhost:8443/fineract-provider/api/v1/runreports/FullReportsList?genericResultSet=false¶meterType=true&tenantIdentifier=default]/[fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund&genericResultSet=false¶meterType=true|https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund&genericResultSet=false¶meterType=true])
and 2. fullReportList.not.found (for: [https://localhost:8443/fineract-provider/api/v1/runreports/FullReportsList?genericResultSet=false¶meterType=true&tenantIdentifier=default]).
Before this commit, there was no exception thrown. so that's why it was working fine.
I tested it by adding these two parameters in the table stretchy_report the report_name's as "ReportCategoryList" and "FullReportList" and it got fixed. Thanks.
was (Author: rrpawar):
[~vorburger] Yes, this commit was throwing the exception for:
1. reportCategoryList.not.found (for: [https://localhost:8443|https://localhost:8443/fineract-provider/api/v1/runreports/FullReportsList?genericResultSet=false¶meterType=true&tenantIdentifier=default]/[fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund&genericResultSet=false¶meterType=true|https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund&genericResultSet=false¶meterType=true])
and fullReportList.not.found (for: [https://localhost:8443/fineract-provider/api/v1/runreports/FullReportsList?genericResultSet=false¶meterType=true&tenantIdentifier=default]).
Before this commit, there was no exception thrown. so that's why it was working fine.
I tested it by adding these two parameters in the table stretchy_report the report_name's as "ReportCategoryList" and "FullReportList" and it got fixed. Thanks.
> Reporting meta-data entry not found - All reports modules
> ---------------------------------------------------------
>
> Key: FINERACT-1306
> URL: https://issues.apache.org/jira/browse/FINERACT-1306
> Project: Apache Fineract
> Issue Type: Bug
> Components: Reports
> Affects Versions: 1.5.0
> Reporter: Francis Guchie
> Assignee: Rahul Pawar
> Priority: Major
> Fix For: 1.5.0
>
> Attachments: image-2021-01-27-09-41-45-780.png
>
>
> [https://ipaddress/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund&genericResultSet=false¶meterType=true|https://diprom.biz/fineract-provider/api/v1/runreports/reportCategoryList?R_reportCategory=Fund&genericResultSet=false¶meterType=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" }
> ]
> }
> ]
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)