409 Conflict error on "Confirmed" contacts

[MegaphoneJon]

[I'm reporting this so it's documented for other potential users/yourself, but I'm not asking for this to be fixed! If it was important enough, I'd do it myself or get a client to fund it.]

If a contact is marked as "Confirmed", the extension can't sync them. The solution suggested here is to use the Bulk API instead - but that's not a trivial undertaking.

I did some testing to see if we could just not pass the email address in on contact update - but that's a required value for the API.

[nganivet]

Yes, definitely not a trivial change. Specifically as this would be a
trivial change on the CtCt side to correct this 'limitation' of theirs:
just compare the newly supplied email with what they have on file, and
if same do not do the update. Thanks for pointing this out Jon.

------ Original Message ------
From: "Jon" [email protected]
To: "cividesk/com.cividesk.sync.constantcontact"
[email protected]
Sent: 3/17/2016 10:53:32 AM
Subject: [com.cividesk.sync.constantcontact] 409 Conflict error on
"Confirmed" contacts (#2)

[I'm reporting this so it's documented for other potential
users/yourself, but I'm not asking for this to be fixed! If it was
important enough, I'd do it myself or get a client to fund it.]

If a contact is marked as "Confirmed", the extension can't sync them.
The solution suggested here is to use the Bulk API instead - but that's
not a trivial undertaking.

I did some testing to see if we could just not pass the email address
in on contact update - but that's a required value for the API.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub