Re: Using mapper key and mapper value to create templates

[Christopher Stewart]

Hello all,

I am still to receive a response on the problem of creating templates. Can
someone please point me in the right direction or towards the right
resources?

Thanks in advance.

Rgds

Chris

On Jan 24, 2017 11:24 AM, "Christopher Stewart" <
christopher.mckenzie.stew...@gmail.com> wrote:

> 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=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" <rajanmaurya...@gmail.com> 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.
>>

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=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" <rajanmaurya...@gmail.com> 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
>> >
>

Re: [Mifos-users] Creating unique external ID in mifos x

[Christopher Stewart]

Hello Nazeer,

Thank you very much for your input. I will consider the Jira option.

Regards,

Chris

On Fri, Jan 20, 2017 at 5:55 PM, Shaik Nazeer <
nazeer.sh...@confluxtechnologies.com> wrote:

> Yes, customer identifiers will be added after creating a client and there
> is no option to create a data table with unique column definition so that
> it will be linked to client entity data table check.
>
> You can raise an enhancement ticket in Jira. I hope some community member
> implements this task.
>
>
>
> Thanks,
>
> Nazeer
>
> Principal Architect, Conflux Technologies Pvt Ltd
> <http://www.confluxtechnologies.com/>
>
> Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block, Bengaluru,
> Karnataka, 560043 INDIA
>
> [image: unnamed]
>
> Disclaimer: The information contained in this e-mail message and any
> files/attachment transmitted with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
>
>
>
> *From:* Christopher Stewart [mailto:christopher.mckenzie.stew...@gmail.com]
>
> *Sent:* 20 January 2017 12:06
> *To:* A good place to start for users or folks new to Mifos.
> *Cc:* dev (dev@fineract.incubator.apache.org); Rajan Maurya
> *Subject:* Re: [Mifos-users] Creating unique external ID in mifos x
>
>
>
> Hi Nazeer,
>
>
>
> I require the national ID to be mandatory when creating a new client.
> Right now a client can be created without an identifier even though it is
> unique.
>
>
>
> Rgds
>
>
>
> Chris
>
>
>
> On Jan 20, 2017 11:11 AM, "Nazeer Shaik" <nazeer.shaik@
> confluxtechnologies.com> wrote:
>
> National ID should be part of the customer identifier and it is already
> unique.
> Can you explain bit more why it should be part of entity data table check?
>
>
> Thanks,
> Nazeer
>
> *Principal Architect, **Conflux Technologies Pvt Ltd
> <http://www.confluxtechnologies.com/>*
>
> *Address*: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
> Bengaluru, Karnataka, 560043 INDIA
>
> Disclaimer: The information contained in this e-mail message and any
> files/attachment transmitted with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorized review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
>
>
>
> 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" <rajanmaurya...@gmail.com> 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 Andro

Creating unique external ID in mifos x

[Christopher Stewart]

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" <rajanmaurya...@gmail.com> 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!  <https://twitter.com/musonimfi>
> > 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 instalment compared to today's schedule. Could you let me
> know
> >> where we are going wrong, or whether this is actually a bug?
> >>
> >> Thanks,
> >> Sander
> >>
> >>
> >>
> >> On 12 December 2016 at 06:20, Adi Raju <adi.raju@confluxtechnologies.
> com>
> >> wrote:
> >>
> >>> Interest calculation on future dates will be based on the assumption
> >>> that payment has been made up-to-date and assuming no arrears.
> >>> Interest on the unpaid or compounded amount will be calculated and
> >>> provided as part of schedule only till as of that day.
> >>>
> >>> So in the example,
> >>> EMI is due on 1st  Dec and 2nd Jan. No repayment is made as of today
> >>> (12/12).
> >>> So interest calculation will be as follows:
> >>> Interest on com

Re: Connecting mifos Android app

[Christopher Stewart]

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
> 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 instalment compared to today's schedule. Could you let me know
>> where we are going wrong, or whether this is actually a bug?
>>
>> Thanks,
>> Sander
>>
>>
>>
>> On 12 December 2016 at 06:20, Adi Raju 
>> wrote:
>>
>>> Interest calculation on future dates will be based on the assumption
>>> that payment has been made up-to-date and assuming no arrears.
>>> Interest on the unpaid or compounded amount will be calculated and
>>> provided as part of schedule only till as of that day.
>>>
>>> So in the example,
>>> EMI is due on 1st  Dec and 2nd Jan. No repayment is made as of today
>>> (12/12).
>>> So interest calculation will be as follows:
>>> Interest on compounded amount as of 1 Dec for 11 days (1st to 12th of
>>> dec)
>>> Plus
>>> Interest on amount as per original schedule for 21 days (13th dec to 2nd
>>> of jan)
>>>
>>> As and when interest recalculation job runs every day, interest will be
>>> revised to include calculations as of that day.
>>>
>>> Regards,
>>> Adi Raju
>>>
>>> Principal Architect, Conflux Technologies Pvt Ltd
>>> Address: #304, 2nd Floor, 7th Main Road, HRBR Layout 1st Block,
>>> Bengaluru, Karnataka, 560043 INDIA
>>>
>>>
>>> Disclaimer: The information contained in this e-mail message and any
>>> files/attachment transmitted with it is confidential and for the sole use
>>> of the intended recipient(s) or entity identified. If you are not the
>>> intended recipient, please email: supp...@confluxtechnologies.com and
>>> destroy/delete all copies and attachment thereto along with the original
>>> message. Any unauthorised review, use, disclosure, dissemination,
>>> forwarding, printing or copying of this email or any action taken in
>>> reliance on this e-mail is strictly prohibited and is unlawful. The
>>> recipient acknowledges that Conflux Technologies Private Limited or its
>>> subsidiaries and associated companies are unable to exercise control or
>>> ensure or guarantee the integrity of/over the contents of the information
>>> contained in e-mail transmissions. Before opening any attachments, please
>>> check.
>>>
>>>
>>>
>>> -Original Message-
>>> From: Sander van der Heyden [mailto:sandervanderhey...@musonisystem.com]
>>> Sent: 09 December 2016 22:08
>>> To: dev@fineract.incubator.apache.org
>>> Cc: A good place to start for users or folks new to Mifos.
>>> Subject: Re: