Chris Travers wrote: > Currenty, in trunk, all addresses, contact info, etc are mapped back > to a company or person entity. We do not have mappings per > customer/vendor account. > > I have had at least one request for contract (entity_credit_account) > to address mappings in the following way: > 1) Every entity_credit_account can only have one billing address > 2) Any number of contacts per entity_credit_account record > 3) One bank account listed per entity_credit_account (for automated payments) > 4) Notes that can be attached to either the entity or contract > > I suspect that there could be a more general need for billing and > contact to map to actual customer accounts than is just with this > company, so I am asking whether everyone else feels like the above > rules are generally applicable. Any thoughts?
Are the instances of 'contract' typos for 'contact'? ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
