That's very helpful thanks. I was only looking at tables as I have an
import requirement for some existing addresses and I hadn't noticed the
service you mentioned, but I'm sure that will make the process easier.
I'll need to dig a little deeper though as I don't want to trigger the
email verification.
Thanks for the hint,
Ray
Hans Bakker wrote:
> Hi Ray,
>
> using the services is always preferred above direct table updates. You do not
> need to know the table structure in this case.
>
> If i check the services list in web tools i find the 'signUpForContactList'
> service. This service does not need a partyId, just an email address will
> do.....
>
> i hope this helps.....
>
> regards,
> Hans
>
> On Friday 02 March 2007 01:14, Ray Barlow wrote:
>
>> Hi,
>>
>> Any pointers about which are the essential records required to subscribe
>> a person to a contact list for an email newsletter. Specifically for
>> people that don't have an account in the system, so no party id or login
>> exists, somebody that might like you're site but only wants to subscribe
>> to the newsletter for now.
>>
>> I see the party id is a primary key on the ContactListParty entity so
>> I'm guessing essentials would be:
>> Party of type PERSON
>> Contact of type EMAIL_ADDRESS
>> ContactListParty
>>
>> optional:
>> PartyContactMechPurpose of type PRIMARY_EMAIL
>>
>> Any others?
>>
>> Ray
>>
>
>
Locked
