I have not forgot just takes time to go back over what I did. ========================= 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> Adam Heath sent the following on 4/21/2010 3:59 PM: > BJ Freeman wrote: >> just off the top of my head we have links by partyID >> https://trunk-demo.ofbiz.apache.org/partymgr/control/viewprofile?portalPageId=PartyProfile&partyId=Company&editPartyRel=Y > > That doesn't solve the problem. > > Shipments and OrderItemShipGroup have a link to a ContactMech. > CreditCard has a singleton link to a ContactMech. Facility can have > multiple contact mechs. (This is not inclusive) > > All of these assocsiated ContactMech may need to be grouped. Consider > the case of a PostalAddress(billing), primary contact number, and > secondary contact number, to be used when sending a shipment to some > location. > > Or a credit card having a billing address, and a telecom number. > > > > > >> ========================= >> 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> >> >> >> Adam Heath sent the following on 4/21/2010 3:12 PM: >>> I see a thread(1) about ContactMech being related to another >>> ContactMech, from back in October. I don't however see any >>> implementation of using ContactMechLink(or a new ContactMechAssoc). >>> >>> My suggestion would be to not create a new entity, as then we would >>> not be following the data model books. However, I do suggest having a >>> ContactMechLinkType entity, and adding such a field to ContactMechLink. >>> >>> Is there any actual implementation for this? >>> >>> >>> 1: >>> http://www.google.com/url?sa=t&source=web&ct=res&cd=1&ved=0CAYQFjAA&url=http%3A%2F%2Fwww.pubbs.net%2F200910%2Fofbiz%2F18563-question-about-best-way-to-group-together-contact-mechs.html&rct=j&q=ofbiz+ContactMechLink&ei=W3PPS8SFLoKclgeO9qSfCw&usg=AFQjCNGjnbI457QAesgx_mgdikSh6nqDWw >>> >> > >
