In that case you might want to remove the XBRL related API calls (Mix
Mapping, Mix Report, Mix Taxonomy) and the related code from your code
base - but I leave this to you.

I remove the feature from the UI.


On 30/03/2025 03:07, James Dailey wrote:
Felix - gotcha

Yes, you’re part of the effort to trim functionality at Mifos AdminUI to
make sure it’s fully usable.

Yes. Remove this non working feature is my recommendation, as the Fineract
APIs will not support it.

James


On Sat, Mar 29, 2025 at 2:07 PM Felix van Hove <fvanh...@gmx.de.invalid>
wrote:

Ed's understanding is spot on: The web app team is currently aiming at a
first official release 1.0.0, and in this context I'm testing every
existing feature of the web app in reach (to the degree my very limited
knowledge of finance allows). There are three possibilities, if a
feature doesn't work:

- Fix it,
- remove it (e.g. everything Self Service),
- grey it out (and add to the release note a remark "currently
unavailable") (e.g. JLG loan applications)

Leave something broken in place is not an option.

For XBRL along with MIX, I understand your comments as: "remove it".
Correct?

Felix

On 29/03/2025 19:24, Ed Cable wrote:
James,

I think Felix is simply trying to go through web app and identify where
there are portions that are broken and not working and this came up.

Just as additional historical context on XBRL, here's some of the
documentation related to that GSOC project:

https://mifosforge.jira.com/wiki/spaces/projects/pages/15433859/XBRL+Reporting+Integration
and discussion: https://groups.google.com/g/mifosdeveloper/c/ewdKtmnuB04

Ed

On Sat, Mar 29, 2025 at 10:52 AM James Dailey <jdai...@apache.org>
wrote:

Felix

Thanks for noticing that functionality.  Can you tell me why you need
it?

The XBRL report feature dates back to my efforts in 2004-2005 to link
the
Mifos project to the reporting infrastructure for "Rating MFIs" that the
Mix Market at CGAP (World Bank) had established.  The intention was to
create a kind of market pull - if an MFI (Microfinance Institution)
could
have a XBRL format go directly to MIX data-system then they could be
rated
quickly and highly, leading to better transparency and potentially more
on-lending funds.  Today the Mix market is gone, or evolved into Findex
datasets, with less focus on this sort of thing.

I wrote some early documentation and attended a couple of XBRL
conferences, where I learned that this standard was still pretty much in
its infancy.  Since then the SEC has adopted it for reporting. 2024 ==>
https://www.sec.gov/files/edgar/xbrl-guide.pdf.

So, here at Fineract, I believe that the relevant thing is to deprecate
this feature (which is actually at Mifos Reports, not here) AND to
recognize that from a reporting perspective, having a feature that can
auto
generate regulatory reporting is an important item.

The first step would be to see what XBRL formats are needed for Bank and
NBFI (Non Banking Financial Institution) Reporting.  This may start with
SARS. (system activity reports) and similar.  It may be that the
requirement here is to have a "read only" API for reporting for
regulatory
purposes.  There's a lot of design that needs to happen for that.

I have a longer post I'm working on - so... please do let me know how
this
relates to your specific needs?  Market requirement?

Thanks,

James




On Sat, Mar 29, 2025 at 10:18 AM Ed Cable <edca...@mifos.org> wrote:

Good question Felix. Mifos, prior to transition to Apache Fineract, had
been supporting the XBRL format as it had been identified and chosen
by MIX
market as a standardized reporting format for the microfinance
industry. So
that is why we had an intern work on an integration and support of that
format. I believe XBRL was a bit overkill for what MIX was aiming for
the
industry overall and those standardization efforts died out.

That being said, it would probably be good to deprecate this
functionality and not expose current users to it via the UI. However if
there are others who are needing report in the XBRL format and are
actively
using I will let them voice their opinion as Bharath has raised.

Ed

On Fri, Mar 28, 2025 at 7:12 AM Felix van Hove <fvanh...@gmx.de.invalid

wrote:

Hi everyone,

Does Fineract support XBRL resp. MIX ? The UI has respective forms,
but
all requests fail and I can't find a ticket regarding this in
Fineract's
Jira.

The only documentation I found is this:


https://docs.mifos.org/mifosx/user-manual/for-all-users/reports/xbrl-reporting
. I'm therefore not even sure the parameters used by the UI currently
for the PUT /v1/mixmapping are correct. Can you point me to any
documentation?

Calling /v1/mixmapping I get a 400 or 500, e.g.

--- snip ---
2025-03-28 14:21:49.975 - WARN 7056  --- [nio-8443-exec-3]
o.m.jdbc.message.server.ErrorPacket      : Error: 1406-22001: Data too
long for column 'config' at row 1
[EL Warning]: 2025-03-28
14:21:49.976--UnitOfWork(809753073)--Exception
[EclipseLink-4002] (Eclipse Persistence Services -
4.0.2.v202306161219):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: (conn=13) Data
too
long for column 'config' at row 1
Error Code: 1406
Call: UPDATE `mix_taxonomy_mapping` SET `identifier` = ?, `config` = ?
WHERE (`id` = ?)
           bind => [3 parameters bound]
Query:


UpdateObjectQuery(org.apache.fineract.mix.domain.MixTaxonomyMapping@685f8ad5
)
2025-03-28 14:21:50.013 - WARN 7056  --- [nio-8443-exec-3]
o.a.f.i.c.e.DefaultExceptionMapper       : Exception occurred

jakarta.persistence.RollbackException: Transaction "rolled back"
because
transaction was set to RollbackOnly.
           at


org.eclipse.persistence.internal.jpa.transaction.EntityTransactionImpl.commit(EntityTransactionImpl.java:146)
           at


org.springframework.orm.jpa.JpaTransactionManager.doCommit(JpaTransactionManager.java:562)
           at


org.apache.fineract.infrastructure.core.persistence.ExtendedJpaTransactionManager.doCommit(ExtendedJpaTransactionManager.java:64)
           at


org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:795)
--- snip ---



Calling GET


/fineract-provider/api/v1/mixreport?startDate=2025-01-01&endDate=2025-01-05
I get a 403, response body:

--- snip ---
{
     "developerMessage": "Request was understood but caused a domain
rule
violation.",
     "httpStatusCode": "403",
     "defaultUserMessage": "Errors contain reason for domain rule
violation.",
     "userMessageGlobalisationCode":
"validation.msg.domain.rule.violation",
     "errors": [
       {
         "developerMessage": "Mapping does not exist",
         "defaultUserMessage": "Mapping does not exist",
         "userMessageGlobalisationCode":
"error.msg.xbrl.report.mapping.invalid.id",
         "parameterName": "id",
         "args": [
           {
             "value": "Mapping is empty"
           }
         ]
       }
     ]
}
--- snip ---

I don't see an "id" parameter in the swagger.

Felix



--
*Ed Cable*
President/CEO, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org
<http://facebook.com/mifos>  <http://www.twitter.com/mifos>







Reply via email to