how about a contactlistappl that other entities can use in the future change the contactlistid to the contactlistappl. then would also a allow a upfrade path with a service.
Ean Schuessler sent the following on 12/12/2010 4:50 PM:
Currently, contact lists are associated with marketing campaigns via a contactListId field on ContactList. It seems to me that contact lists would be used repeatedly over a long period of time by numerous campaigns. Would there be an objection to deprecating the marketingCampaignId field in ContactList and creating a new MarketingCampaignContactList entity? I would imagine that this entity would follow the fromDate/thruDate pattern.
