Hi Shannon, We are encountering this issue while using existing event objects retrieved as follows (referring to .NET SDK EventSpotService methods): 1. Call GetAllEventSpots to get collection of events, then filter collection by those with start dates meeting a cutoff date (X days ago). 2. Use the IDs from the filtered events collection to create a new collection of IndividualEvent (CC event) objects by calling GetEventSpot for each event ID. We need the full event record so we can access the UpdateDate field for purposes of synchronization. [Feature request... add UpdateDate to GetAllEventSpots results as well as some query parameters to limit the results ] Then, for each event in that collection... 3. Check whether we have an event record in our database with a 'CCEventID' value matching the IndividualEvent.Id. When no event record exists in our database... 4. Create a new event record in our database and record the IndividualEvent.Id value as 'CCEventID' in that record for future synchronizations. 5. Update the IndividualEvent (retrieved using GetEventSpot from step 2) using PutEventSpot so that we update its UpdateDate value to reflect the date/time of the current synchronization. No changes are made to the IndividualEvent before calling PutEventSpot. (We've also taken the path of waiting until a later sync to update the UpdateDate, but the end result is the same.) No call to PostEventSpot is made during this process, yet it results in a second event of the same name displayed in our My Campaigns list in the CC UI. In our most recent test to reproduce this issue, we created an event that had and Id value of: a07eareeuvn59f1d9db (observed on IndividualEvent object during debugging). The CC Id value recorded in the event record in our database was: a07eareeuvn59f1d9db The CC Id value for that event shown in the API tester's GET method is: a07eareeuvn59f1d9db (call made after sync completed) If a true duplicate CC event was created with a new Id value, we would see a companion duplicate event record in our database upon subsequent synchronizations, but no such duplicates are occurring. So in summary we appear to be working with the event object pulled from CC, updating it, and sending it back without changing the ID, yet this process results in a duplicate of the event appearing (and only one of the duplicate links works; the other causes the error page to appear). Please let me know if there is any other information I can provide. Thanks, Chuck
... View more