Re: Dev - do we need Invoice.billingAccountId and contactMechId?
Posted by
Si Chen-2 on
May 09, 2006; 5:04pm
URL: http://ofbiz.116.s1.nabble.com/Dev-do-we-need-Invoice-billingAccountId-and-contactMechId-tp167896p167898.html
This is interesting because we don't have any other payment method that
is directly associated with an invoice in the Invoice (header) entity.
Usually we have a more normalized model, but I guess if it works, then
let's keep it.
What about contactMechId? Is that used right now? If not, do we need
it? Because we do have InvoiceContactMech...
Si
David E Jones wrote:
I think the answer is a definite yes... This should be the one and only way to associate an Invoice with a BillingAccount.
It is true that the PaymentApplication entity has sufficient fields to do this, but it should _never_ be used for that, it is a "PaymentApplication" after all, and not an "Invoice Application". So, when getting the list of Invoices related to a BillingAccount the Invoice.billingAccountId is the one that should be used...
-David
Si Chen wrote:
Hi everybody -
Do we need the fields on "billingAccountId" and "contactMechId" on
Invoice entity? Is anyone using them for any purpose?
Si
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev