can't apply client charges to clients

[Emmanuel Njoku <ei...@gmail.com>]

Good day All,

please assist with this error below.

 Financial Activity account with for the financial Activity with Id 103
does not exist

Financial activity account needed for this operation has not been defined.

Kindly assist on the step to create  Financial activity account for this
operation.

On Mon, Jul 23, 2018 at 12:01 PM, Gaurav Saini <ga...@gmail.com>
wrote:

> Hello Anwesh and Abhay,
>
> I would say it is good to use as much space as possible, otherwise use
> have to scroll down when we have a lot many fields in forms. For Stepper I
> would say stick to what angular material officially provides.
>
> Also, One thing to note is that you both should work in parallel and
> follow same approach otherwise there will be re-work either way. One of the
> reason to select strictly angular material is there is symmetry in code and
> no one applies hacks or custom components/libraries. Please try to
> co-originate and work in a team :)
>
> Thanks
> Gaurav
>
> On Fri, Jul 20, 2018 at 10:28 PM Anwesh Krishna Nayak <
> anweshknayak@gmail.com> wrote:
>
>> It can't be done later. It will be quite tedious to change things over
>> and over as we have gone through it already. It takes a lot of time for UI
>> and also for responsiveness.
>>
>> So if we could quickly finalized which one to be used. Just to be clear
>> the current angular wizard is purely material and has no issues.
>>
>> On Fri, Jul 20, 2018 at 10:10 PM, Abhay Chawla <ab...@gmail.com>
>> wrote:
>>
>>> I understand it is time-consuming. It has been the same for me.
>>>
>>> Although it might not be possible to change where it has been
>>> implemented right now due to time constraints, it would be helpful if there
>>> could be some clarity regarding which approach to be followed so that it
>>> can be implemented for the components that are left to be implemented.
>>>
>>> Anwesh and I have used different approaches and later in time one of us
>>> will have to update but it can be done later so that we can progress
>>> further right now.
>>>
>>> For now, if I could have some clarity the new components can be
>>> implemented accordingly.
>>>
>>> Abhay.
>>>
>>> On Fri, Jul 20, 2018 at 9:52 PM Anwesh Krishna Nayak <
>>> anweshknayak@gmail.com> wrote:
>>>
>>>> I think we should stick to the former with single column.
>>>>
>>>>  Also I have done most of the work based on on already. It will be time
>>>> talking to change things again. As few weeks are left and thing needs to be
>>>> moving rapid. Also I discussed the same with Santosh.
>>>>
>>>> We have already changed from ng bootstrap to material. It was time
>>>> consuming. I say let's not waste more time.
>>>>
>>>> Moreover the purpose of single column is that we could divide it into
>>>> various wizards. So that it will be easy to fill up. Previous form design
>>>> in community app was similar to the two column which had many
>>>> inconsistencies I faced during fixing it and making it responsive was more
>>>> tedious.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, 20 Jul 2018, 21:22 Abhay Chawla, <ab...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Everyone,
>>>>>
>>>>> This is regarding the current design implementation in the web app.
>>>>> Currently, wherever we have forms it was decided that we follow a single
>>>>> column approach along with the implementation of angular-archwizard.
>>>>> According to me, we have a lot of space on larger screens like
>>>>> desktops where due to this a lot of space remains vacant on the left and
>>>>> right side. Therefore I think we should follow a two column approach for
>>>>> larger screens and single column for smaller screens only.
>>>>> Also, we should use the angular material stepper instead of angular
>>>>> archwizard as although the angular archwizard supports the case to disable
>>>>> the wizard view if its not required, it has only been updated to support
>>>>> Angular 5 till now. Instead material stepper can be used where wizard view
>>>>> is required and simple material card design approach be used where it isn't.
>>>>>
>>>>> @Gaurav @Pranjal @Maulik @Santosh @Ed please let us know your opinion
>>>>> regarding the same.
>>>>> I have attached screenshots for the single column and two column
>>>>> approaches for your reference.
>>>>>
>>>>> Thanks
>>>>> Abhay.
>>>>>
>>>>
>>
>
> --
> Regards,
> *Gaurav Saini*
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> Mifos-developer mailing list
> mifos-developer@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>

RE: can't apply client charges to clients

[Louis Niyongabo <ln...@gmail.com>]

Emmanuel,
Would you try set Accounting/Financial Activity Mappings/Define New Mapping, select from the drop down "Fund Source" and link it to an Asset Account and see if it gets fixed?
May I know what you were trying to do?
Thanks,
Louis


-----Original Message-----
From: Emmanuel Njoku [mailto:einjoku@gmail.com] 
Sent: Monday, July 23, 2018 14:53
To: Mifos software development <mi...@lists.sourceforge.net>
Cc: Anwesh Krishna Nayak <an...@gmail.com>; Pranjal Goswami <pr...@gmail.com>; Maulik Soneji <ma...@gmail.com>; Dev <de...@fineract.apache.org>
Subject: can't apply client charges to clients

Good day All,

please assist with this error below.

 Financial Activity account with for the financial Activity with Id 103 does not exist

Financial activity account needed for this operation has not been defined.

Kindly assist on the step to create  Financial activity account for this operation.

On Mon, Jul 23, 2018 at 12:01 PM, Gaurav Saini <ga...@gmail.com>
wrote:

> Hello Anwesh and Abhay,
>
> I would say it is good to use as much space as possible, otherwise use 
> have to scroll down when we have a lot many fields in forms. For 
> Stepper I would say stick to what angular material officially provides.
>
> Also, One thing to note is that you both should work in parallel and 
> follow same approach otherwise there will be re-work either way. One 
> of the reason to select strictly angular material is there is symmetry 
> in code and no one applies hacks or custom components/libraries. 
> Please try to co-originate and work in a team :)
>
> Thanks
> Gaurav
>
> On Fri, Jul 20, 2018 at 10:28 PM Anwesh Krishna Nayak < 
> anweshknayak@gmail.com> wrote:
>
>> It can't be done later. It will be quite tedious to change things 
>> over and over as we have gone through it already. It takes a lot of 
>> time for UI and also for responsiveness.
>>
>> So if we could quickly finalized which one to be used. Just to be 
>> clear the current angular wizard is purely material and has no issues.
>>
>> On Fri, Jul 20, 2018 at 10:10 PM, Abhay Chawla 
>> <ab...@gmail.com>
>> wrote:
>>
>>> I understand it is time-consuming. It has been the same for me.
>>>
>>> Although it might not be possible to change where it has been 
>>> implemented right now due to time constraints, it would be helpful 
>>> if there could be some clarity regarding which approach to be 
>>> followed so that it can be implemented for the components that are left to be implemented.
>>>
>>> Anwesh and I have used different approaches and later in time one of 
>>> us will have to update but it can be done later so that we can 
>>> progress further right now.
>>>
>>> For now, if I could have some clarity the new components can be 
>>> implemented accordingly.
>>>
>>> Abhay.
>>>
>>> On Fri, Jul 20, 2018 at 9:52 PM Anwesh Krishna Nayak < 
>>> anweshknayak@gmail.com> wrote:
>>>
>>>> I think we should stick to the former with single column.
>>>>
>>>>  Also I have done most of the work based on on already. It will be 
>>>> time talking to change things again. As few weeks are left and 
>>>> thing needs to be moving rapid. Also I discussed the same with Santosh.
>>>>
>>>> We have already changed from ng bootstrap to material. It was time 
>>>> consuming. I say let's not waste more time.
>>>>
>>>> Moreover the purpose of single column is that we could divide it 
>>>> into various wizards. So that it will be easy to fill up. Previous 
>>>> form design in community app was similar to the two column which 
>>>> had many inconsistencies I faced during fixing it and making it 
>>>> responsive was more tedious.
>>>>
>>>> Thanks
>>>>
>>>> On Fri, 20 Jul 2018, 21:22 Abhay Chawla, <ab...@gmail.com>
>>>> wrote:
>>>>
>>>>> Hello Everyone,
>>>>>
>>>>> This is regarding the current design implementation in the web app.
>>>>> Currently, wherever we have forms it was decided that we follow a 
>>>>> single column approach along with the implementation of angular-archwizard.
>>>>> According to me, we have a lot of space on larger screens like 
>>>>> desktops where due to this a lot of space remains vacant on the 
>>>>> left and right side. Therefore I think we should follow a two 
>>>>> column approach for larger screens and single column for smaller screens only.
>>>>> Also, we should use the angular material stepper instead of 
>>>>> angular archwizard as although the angular archwizard supports the 
>>>>> case to disable the wizard view if its not required, it has only 
>>>>> been updated to support Angular 5 till now. Instead material 
>>>>> stepper can be used where wizard view is required and simple material card design approach be used where it isn't.
>>>>>
>>>>> @Gaurav @Pranjal @Maulik @Santosh @Ed please let us know your 
>>>>> opinion regarding the same.
>>>>> I have attached screenshots for the single column and two column 
>>>>> approaches for your reference.
>>>>>
>>>>> Thanks
>>>>> Abhay.
>>>>>
>>>>
>>
>
> --
> Regards,
> *Gaurav Saini*
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most 
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot 
> Mifos-developer mailing list mifos-developer@lists.sourceforge.net
> Unsubscribe or change settings at:
> https://lists.sourceforge.net/lists/listinfo/mifos-developer
>