Hey Bharat, Thanks for putting together this thread.
As Saransh pointed out, not only integration of Pentaho with latest
versions started extinguishing, I have noticed that this Pentaho
integration misses out a lot more requirements.

*3.* Clearly, a new external open solution needs to be integrated because
of the following scenarios:
a.) No ability for generating an external feed of reporting which many FIs
wish to use to report to their different Information Systems. I am talking
about file interchange format feeds. (CSV, excel is a limited function.)
b.) Reports are not highly configurable as we promise with Pentaho. Of
Course, those with SQL knowhow can customize them. But somehow we have
missed out the aspect of this for non technical functional experts
routinely managing the system configuration of Fineract via community app.
Pentaho does not help in this direction.
c.) There is no user level encryption of the reports getting fired and up
for download, also at API level.(which of course can be extended & executed)
d.) The direct end points of granular level reporting(e.g accounting
reports in pentaho) are again missing which is increasingly becoming a
standard point of Financial reporting. e.g if an FI wishes to push their
portfolio reporting for an external securitization or better if Risk
reporting solutions need to be embedded, Pentaho does not support this to
the extent of 2020 level reporting.

I would be happy to point a functional specification on a Jira Issue. Prior
to that, I am looking for a technical conversation of feasibility on this

On Tue, Jun 30, 2020 at 9:22 AM Bharath Gowda <bgo...@mifos.org> wrote:

> Hello Everyone,
> Initiating this thread to understand and discuss a solution for the
> Pentaho reporting issues which has surfaced recently.
> 1. From which version, Fineract has stopped supporting Pentaho due to
> Licencing issues?
> 2. When we run a Pentaho report on Develop version, we get an sql
> injection error like below, Will it be appropriate to raise an issue to
> handle the pentaho errors (if it is due to the licence support issue) which
> will help the users to understand better?
> {"developerMessage":"The request was invalid. This typically will happen
> due to validation errors which are
> provided.","httpStatusCode":"400","defaultUserMessage":"Unexpected SQL
> Commands
> found","userMessageGlobalisationCode":"error.msg.found.sql.injection
> 3. Should we discuss an alternate solution for this? Our stretchy reports
> have limitations, many value added reports (with design and calculations)
> will not work with stretchy reports.
> From an organization users perspective, this might become a bottleneck for
> their End/Beginning of the Day/Month/Year Business Reconciliations.
> Regards,
> Bharath
> Lead Implementation Analyst | Mifos Initiative
> Skype: live:cbharath4| Mobile: +91.7019636073
> http://mifos.org  <http://facebook.com/mifos>
> <http://www.twitter.com/mifos>
> On Tue, Jun 30, 2020 at 12:02 AM Saransh Sharma <sara...@muellners.org>
> wrote:
>> Currently fineract does not support Pentaho reports due to Licensing
>> issues.
>> You can use or integrate some oss version of reporting engine if you
>> want.
>> Thanks
>> Though Inbuilt Sql based reporting is also quite usable and powerful.
>> On Mon, 29 Jun 2020, 23:11 Kalanzi Vincent, <vincentkalanzi...@gmail.com>
>> wrote:
>>> Hello Dev
>>> I have an instance running locally from the latest fineract repository
>>> and also have accessed dev.mifos.io
>>> In both cases the Pentaho Reports show blank white screen. Am asking for
>>> guidance on how to utilize Pentaho Reports on fineract
>>> https://github.com/apache/fineract
>>> Kind Regards.
>> Mifos-developer mailing list
>> mifos-develo...@lists.sourceforge.net
>> Unsubscribe or change settings at:
>> https://lists.sourceforge.net/lists/listinfo/mifos-developer

Ankit Müllner
Muellners Europe

This mail is governed by Muellners®  IT policy.
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if
this message has been addressed to you in error, please immediately alert
the sender by reply e-mail and then delete this message, including any
attachments. Any dissemination, distribution or other use of the contents
of this message by anyone other than the intended recipient is strictly
prohibited. All messages sent to and from this e-mail address may be
monitored as permitted by applicable law and regulations to ensure
compliance with our internal policies and to protect our business. E-mails
are not secure and cannot be guaranteed to be error free as they can be
intercepted, amended, lost or destroyed, or contain viruses. You are deemed
to have accepted these risks if you communicate with us by e-mail.

Reply via email to