Not sure I fully understand your comment, BJ. It seems to me that we can't assume that updating one (Postal) address updates any or all other matching addresses as well.
The CC address is a billing address that is sometimes transmitted with payment requests, and probably has to match the info your bank has for you, or CC payments may be rejected. That address may or may not change with the invoice address, or any other address. Certainly any change there needs to be made with caution. Shouldn't an address change here simply link the new address (or an existing one, if appropriate) to the contact mechanism "general correspondence", "invoice/payment" or whatever? Why would it need to lookup or verify EFT addresses at all? And shouldn't NameOnAccount be in a separate entity from the address anyway? Or am I reading Silverston wrong? Seems like usually (e.g. for partys, groups, etc), we take the approach of <find> first, or <create> as necessary, then <link> with a relation, in this case contact_mech. Here we throw up an edit screen and collect a contact purpose and address, which is maybe rolling the <find> and <link> together? What changed since 9.04? I would expect this part of the code to be pretty stable. -- Matt Warnock <[email protected]> RidgeCrest Herbals, Inc. On Tue, 2010-05-25 at 14:16 -0700, BJ Freeman wrote: > I agree with you that the postal address must first be varified that it > matches then update. > most CC have and address component that needs update if you change the > contact mech address. > I think an reviews should go back to if the contact mech address is > linked to the cc entity. this way if that contact mech is updated none > of that is necessary. > > > ========================= > BJ Freeman > http://bjfreeman.elance.com > Strategic Power Office with Supplier Automation > <http://www.businessesnetwork.com/automation/viewforum.php?f=93> > Specialtymarket.com <http://www.specialtymarket.com/> > > Systems Integrator-- Glad to Assist > > Chat Y! messenger: bjfr33man > Linkedin > <http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro> > > > Matt Warnock sent the following on 5/25/2010 1:09 PM: > > Thanks BJ. > > > > Looks like it already has a Jira issue, but it isn't fixed yet. > > https://issues.apache.org/jira/browse/OFBIZ-3485 > > > > Anybody know a workaround? > > > > Why do we call updatePaymentMethodAddress if only a PostalAddress is > > involved? I haven't set up any payment methods yet, though maybe some > > are already in the demo data. >
