Ok some more info. In the SFA application i want to be sure a party is only listed in either lead or contact or account and not in two lists. This is independent of any relation
If i create party as a lead then i use this in the partyrelationship entity to have a related partyGroup record for the company name. When i covert the lead to contact I set the enddate on this relationship to keep the history and create a new one for the role 'contact'; Before that i add the role of 'contact' to this party to indicate the conversion. I can however not delete the 'lead' role because it is used in partyrelationship. having a new field on party is a very simple solution and i can change the partyFind service with no effort so one can search on this field. we can also consider to add a 'from/thru' date to the partyrole entity however that is a pretty big change to the system because this entity is used in many places..... On Thu, 2008-06-05 at 21:59 -0600, David E Jones wrote: > > I don't really like the idea of "primary role", as roles don't really > work that way. > > If you don't want a party showing up on a list of leads and contacts, > then they shouldn't have both the lead and contact roles... > > Could you be more specific about what you're trying to do here? > > -David > > > On Jun 5, 2008, at 9:49 PM, Adrian Crum wrote: > > > Why not make it a party relationship? A party is related to this > > party/company/etc as a lead/contact/account/etc. > > > > -Adrian > > > > --- On Thu, 6/5/08, Hans Bakker <[EMAIL PROTECTED]> > > wrote: > > From: Hans Bakker <[EMAIL PROTECTED]> > > Subject: primary Role on party > > To: "user" <[email protected]> > > Date: Thursday, June 5, 2008, 8:08 PM > > > > In the SFA application I need the definition of a 'primary roleType' > > to > > identify where a party is listed...either in leads, contacts or > > accounts... > > > > Anybody any objections when i add this field to the Party entity? > > > > Regards, > > Hans > > > > >
