[ 
https://issues.apache.org/jira/browse/OFBIZ-11181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921728#comment-16921728
 ] 

Parminder edited comment on OFBIZ-11181 at 9/3/19 9:26 PM:
-----------------------------------------------------------

In my older production version the form has the following code (in 
PaymentForms.xml):

 

<field position="2" name="paymentMethodTypeId">
 <drop-down allow-empty="true">
 <entity-options entity-name="PaymentMethodType" description="${description}">
 <entity-order-by field-name="description"/>
 </entity-options>
 </drop-down>
 </field>

 

It has method type id not method id. I  remember tweaking something in this 
form 2-3 years ago but don't remember exactly what. This does show the payment 
method types that we want to see. However, payment method id seems to be 
mandatory field defined in entity definitions, so without it, the system does 
not allow the payment status to be changed to received(in 16.11.05) when I used 
this code.
  

{color:#ff0000}The Following Errors Occurred:{color}

{color:#ff0000}Cannot change the status to 'Received' when the mandatory 
payment method is missing.{color}

 

However, at least it does get past the creation and application step.

Also, in my current production setup the received payment does not credit  
amount to the bank account selected (it should) but since I could not RECEIVE 
THE PAYMENT IN 16.11.05, I could not test that part but these two issues should 
be considered together(if possible).

 


was (Author: plehal):
In my older production version the form has the following code (in 
PaymentForms.xml):

 

<field position="2" name="paymentMethodTypeId">
 <drop-down allow-empty="true">
 <entity-options entity-name="PaymentMethodType" description="${description}">
 <entity-order-by field-name="description"/>
 </entity-options>
 </drop-down>
 </field>

 

It has methid type id not method id. I  remember tweaking something in this 
form 2-3 years ago but don't remember exactly what. This does show the payment 
method types that we want to see. However, payment method id seems to be 
mandatory field defined in entity definitions, so without it, the system does 
not allow the payment status to be changed to received.
 

{color:#FF0000}The Following Errors Occurred:{color}

{color:#FF0000}Cannot change the status to 'Received' when the mandatory 
payment method is missing.{color}

 

However, at least it does get past the creation and application step.

Also, in my current production setup the received payment does not credit  
amount to the bank account selected (it should) but since I could not RECEIVE 
THE PAYMENT IN 16.11.05, I could not test that part but these two issues should 
be considered together(if possible).

 

> paymentMethodId choices wrong in form for creating/editing a received payment
> -----------------------------------------------------------------------------
>
>                 Key: OFBIZ-11181
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11181
>             Project: OFBiz
>          Issue Type: Bug
>          Components: accounting
>    Affects Versions: Trunk, Release Branch 16.11, Release Branch 17.12, 
> Release Branch 18.12
>         Environment: Ofbiz 16.11.05 on Fedora 30 with OpenJDK 64-Bit Server 
> VM (build 25.222-b10, mixed mode) and mariadb-server.x86_64 3:10.3.17-1.fc30 
> as database
>            Reporter: Parminder
>            Assignee: Jacques Le Roux
>            Priority: Major
>
> {color:#737373}There is a bug in the forms   for 
> Payment{color}{color:#737373} method field(drop down) for Incoming payment. 
> Payment methods should be{color}
> {color:#737373} whatever is  defined for getting the payments from customers 
> like  {color}{color:#737373}Company Check, Cash etc. etc. but it is showing 
> the methods which are{color}{color:#737373} applicable for outgoing payments 
> such as Petty cash and defined{color}{color:#737373} Financial accounts (from 
> where you pay the suppliers).{color}



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to