Using mapper key and mapper value to create templates

[Christopher Stewart]

Hello All,

I am having trouble creating template documents, especially with advanced
options using mapper keys and mapper values. For example I need the client
address to be printed on a "Loan" type document and the group members names
and external ID's. This is for the purpose of creating a template for the
loan agreement. However my attempts to get the address printed has failed
so far. Pls see below,

Entity: Loan
Type: Document
Template: Test Agreement

Advanced options -

Mapper Key Mapper Value
loan loans/{{loanId}}?associations=all&tenantIdentifier=default
client2 clients/{{loan.clientId}}?tenantIdentifier=default
Address /client/{clientid}/addresses
The following works perfectly.

Customer Code: {{loan.clientId}} Branch Code:
{{client2.officeName}}
  Loan ID: {{loan.accountNo}}

Loan Officer: {{loan.loanOfficerName}}

Customer Name: {{loan.clientName}}

Customer ID: {{client2.externalId}}


However the below does not-

Street address: {{Address.street}}


I have enabled address in the global configuration and set the value as "1"
but still I cannot get the address to get printed. Any help in using the
mapper key and mapper values to create templates will be greatly
appreciated.


Thanks


Chris

On Fri, Jan 20, 2017 at 10:27 AM, Christopher Stewart <
christopher.mckenzie.stew...@gmail.com> wrote:

> Hello all,
>
> I have a request to ensure that the national ID be a unique and mandatory
> field for all clients. So when a client is created this should be verified.
> I looked at the entity data table check feature but it does not verify the
> entry is unique.
>
> I'm sure this is not a unique requirement and hope someone can help me
> out.
>
> Thanks in advance
>
> Chris
>
> On Jan 11, 2017 1:59 AM, "Rajan Maurya"  wrote:
>
> Hi Christopher,
>
> App code base has changed a lot and working fine.
> I have emailed you the latest APK please check and we are going to
> release the app very soon on play store.
>
>
>
>
> On Tue, Jan 10, 2017 at 3:07 PM, Christopher Stewart <
> christopher.mckenzie.stew...@gmail.com> wrote:
>
>> Hi,
>>
>> Has anyone managed to connect and use the mifos Android client
>> successfully?
>>
>> I see many posts regarding connection failures and I myself are getting
>> the
>> 'there was some issue processing your request' error.
>>
>> My mifos instance is hosted on an ip address and not domain name. Ex:
>> 204.xxx.xxx.xxx/#/ port 80.
>>
>> The isn't version is 3 and I have the November 2016 version of mifos
>> running.
>>
>> Any help would be greatly appreciated.
>>
>> Thanks in advance
>>
>> Chris
>>
>> On Dec 23, 2016 7:48 PM, "Sander van der Heyden" <
>> sandervanderhey...@musonisystem.com> wrote:
>>
>> Hi Adi,
>>
>> We are wondering whether you had a chance to look at the interest
>> calculation excel? We are still unable to reconcile amounts for subsequent
>> instalments.
>>
>> In addition we've also started seeing more problems with loans that are
>> prepaid significantly early on in the schedule, unfortunately I cannot
>> test
>> this on the demo as the ability to create new loans seems to be broken
>> right now.
>>
>> Thanks,
>> Sander van der Heyden
>>
>>
>>
>> On 15 December 2016 at 11:16, Sander van der Heyden <
>> sandervanderhey...@musonisystem.com> wrote:
>>
>> > Hi Adi,
>> >
>> > Was wondering if you had seen my previous mail?
>> >
>> > In addition we've also got an issue when backdating the interest
>> > recalculation loans that have compounding on Interest enabled, and use
>> the
>> > "Same as repayment period" compounding type for interest and principal.
>> > This sample loan (https://demo.openmf.org/#/loanaccount/333/disburse)
>> cannot
>> > be disbursed as a result of an EMI error:
>> > *error.msg.loanschedule.emi.amount.must.be.greter.than.interest*, when
>>
>> > you disburse with date of 1st of October.
>> >
>> > If you try to disburse as per 1st of November then it does work fine,
>> > which leads me to believe there is an issue in the error handling around
>> > compounding for backdated loans. As there are no params on a loan level,
>> > that we can adjust to not trigger interest recalculation when disbursing
>> > I'm not sure how to get around this one?
>> >
>> > Thanks,
>> > Sander
>> >
>> >
>> >
>> >
>> > Sander van der Heyden
>> >
>> > CTO Musoni Services
>> >
>> >
>> >
>> >
>> > Mobile (NL): +31 (0)6 14239505 <+31%206%2014239505>
>> > Skype: s.vdheyden
>> > Website: musonisystem.com
>> > Follow us on Twitter!  
>> > Postal address: Hillegomstraat 12-14, office 0.09, 1058 LS, Amsterdam,
>> > The Netherlands
>> >
>> > On 13 December 2016 at 08:52, Sander van der Heyden <
>> > sandervanderhey...@musonisystem.com> wrote:
>> >
>> >> Hi Adi,
>> >>
>> >> Thanks for your feedback, but not sure whether we can make this
>> >> calculation work, see attached excel using the same logic. It works
>> fine
>> >> for working out instalment one, but does leave us with a 0.4
>> difference on
>> >> the second

Re: Please help evaluation Fineract's readiness for graduation

[Ed Cable]

Markus,

Nazeer is continuing to work on addressing the areas of concern related to
QU10, QU40, and RE50.

Could you provide me access to the Apache Fineract website to address CO10
and then for CS10 do we want that on the Apache Fineract website or the
wiki?

Thanks,

Ed

On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski  wrote:

> Agreed.
>
> > On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
> wrote:
> >
> > On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
> >> Could our Apache Fineract mentors please provide some guidance on a
> couple
> >> of the areas we need to improve upon:
> >>
> >> QU10 "*The project is open and honest about the quality of its code.
> >> Various levels of quality and maturity for various modules are natural
> and
> >> acceptable as long as they are clearly communicated." -*
> >>
> >> Do you have any other projects you could point to that have strong
> >> transparent measures of quality and maturity clearly available We want
> to
> >> follow best practices and adopt similar to display at
> >> http://fineract.incubator.apache.org
> >
> > Regular deployment of tools like Findbugs is a good indication that you
> take
> > this requirement seriously.
> >
> >> *QU30: The project provides a well-documented channel to report security
> >> issues, along with a documented way of responding to them.*
> >>
> >> Currently we just link to: http://www.apache.org/security/ Are we able
> to
> >> do as other projects at http://www.apache.org/security/projects.html
> or is
> >> a private channel not something we can set up till we're out of
> >> incubation.  If we can move forwarde, I'd suggest we have a security
> page
> >> on our site, document and fix known vulnerabilities and then provide
> clear
> >> instruction on reporting vulnerabilities to a private channel like
> >> secur...@fineract.incubator..apache.org
> >
> > This is less about security@fineract vs.  http://www.apache.org/
> security/
> > and more about the community being ready for when the first 0 day
> > hits either of those. Being ready is a combination of tribal knowledge,
> > wiki recommendations and a release policy that would allow you to patch
> > at a drop of a hat.
> >
> > Thanks,
> > Roman.
>
>


-- 
*Ed Cable*
Director of Community Programs, Mifos Initiative
edca...@mifos.org | Skype: edcable | Mobile: +1.484.477.8649

*Collectively Creating a World of 3 Billion Maries | *http://mifos.org