[jira] Commented: (OFBIZ-74) billing account error in checkout

[Nicolas Malin (Jira)]

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

Jacopo Cappellato commented on OFBIZ-74:
----------------------------------------

Jacques,

yes, unfortunately this is still an open issue and the best thing we can do is to try to fix it together with the other issues currently affecting billing accounts (OFBIZ-901).
I have some ideas but no time right now...

> billing account error in checkout
> ---------------------------------
>
>                 Key: OFBIZ-74
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-74
>             Project: OFBiz (The Open for Business Project)
>          Issue Type: Bug
>          Components: ecommerce, order
>            Reporter: Chris Howe
>
> If you have a Credit Card on file and a billing account on file where CreditCard.paymentMethodId = BillingAccount.billingAccountId, you will not have unique names for the order bill up to text boxes (name="amount_${billingAccount.billingAccountId}" and name="amount_${paymentMethod.paymentMethodId}  and the cart will not move to completion if you are trying to "pay" by billing account.
> solution I'm thinking of changes name="amount_${billingAccount.billingAccountId}" to name="amount_BA_${billingAccount.billingAccountId}" and then breaks off the _BA in the event of checkoutoptions uri

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[Michael Irving]

Is there a trick that forces the <lookup></lookup> form widget to use
call_fieldlookup3 instead of using call_fieldlookup2?

-Mike

[jonwimp]

When the attribute "description-field-name" is not empty, the lookup will use call_fieldlookup3.

Jonathon

Michael Irving wrote:
> Is there a trick that forces the <lookup></lookup> form widget to use
> call_fieldlookup3 instead of using call_fieldlookup2?
>
> -Mike
>
>