Michael Vorburger created FINERACT-1173:
-------------------------------------------
Summary: Error Message in case of missing reporting implementation
is confusing
Key: FINERACT-1173
URL: https://issues.apache.org/jira/browse/FINERACT-1173
Project: Apache Fineract
Issue Type: Bug
Reporter: Michael Vorburger
Assignee: Michael Vorburger
Fix For: 1.5.0
While working on FINERACT-1127, I noticed that the Error Message in case of a
missing reporting implementation is pretty damn confusing.. this made it more
cnofusing for me to build https://github.com/vorburger/fineract-pentaho/ for
FINERACT-1127 than I thought this would be.
In 1.4.0 Fineract for a URL like
{{{{API_URL}}/api/v1/runreports/Expected%20Payments%20By%20Date%20-%20Formatted?R_endDate=2013-04-30&R_loanOfficerId=-1&R_officeId=1&R_startDate=2013-04-16&output-type=PDF&R_officeId=1}}
is currently reporting "Reporting meta-data entry not found." (or "Report
Parameter with identifier " + id + " does not exist"; both from
{{ReportNotFoundException}}) - but that's otherwise used for a report that
cannot be found, and bubbles up from much later in the code.
I'll raise a PR so that in 1.5.0 this surfaces much more clearly, and earlier
in the code, as a {{PlatformServiceUnavailableException}} with more more
obvious text: "There is no ReportingProcessService registered in the
ReportingProcessServiceProvider for this report type: "
[~francisguchie] [~ptuomola] FYI.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
