Hey guys, just started working with Splendid and I am really excited about what I am seeing. I am working on getting the outlook Add-in working and ran into this problem:

Everytime Outlook sync's with Splendid, every appointment in outlook is duplicated in Splendid. And what is worse, every appointment is marked as "Planned" even if it occurs in the past, this means that it shows up on the users home page under "My Upcoming Appointments".

Since the settings for the Add-In were set to sync the calendar every 15 minutes, after letting it run overnight, I awoke this morning to having over 4,000 rows of appointments on the home page, all of which occur in the past.

I am a consultant in Seattle, WA evaluating Splendid for use in production for several of my clients. The Outlook integration is a must-have, and obviously this bug is a show stopper for us, however, I have to assume that this is just something I have configured wrong or an easy fix.

Configuration:
Outlook Add-In: 1.0.2436.2475
Splendid: 1.2.2417 patched to 1.2.2436

Brian Jimdar

Thanks for your help.
To answer your question. I have made no modifications to SplendidCRM.
I even setup a new version of Splendid on another server just to make sure that there wasn't some setting that I had messed up.

The version in the About page says: Version 4.2.0 Build 1.2.2439.20213
The outlook add-in About Dialog says: 1.0.2436.2475

The only thing I can think of that I changed was the registry settings for loading the Add-In. When installing the Outlook Add-in, it didn't load at first. I have quite a bit of VSTO experience so I took a look at the registry and noticed that there was no key under \Software\Microsoft\Office\Outlook\Add-Ins for anything that said splendid. So I used Orca to take a peek at what reg keys your MSI wanted installed and entered them in manually. This worked great and the Add-In has been working great except for this problem. I thought I should mention this as it might help, but since I didn't see any reg keys that seemed to have anything to do with calendar sync, I assume that this wouldn't have any bearing on this problem.

When you click the "Sync Calendar" button on the Splendid Toolbar in outlook, the pop-up dialog says:

...
Sending Appointment 2 to CRM
Sending Appointment 1 to CRM
0 Appointments exist in CRM; 62 are new, 0 are modified 31 were modified in Outlook, 0 are in conflict.
Retrieving relationships from CRM...
Connecting to CRM...

Then after it's done, I get the following error in a MessageBox:

Void SyncCalendar(Boolean) Line 1976.
Item has already been added. Key in dictionary: '' key being added: ''

Not having the source code to the Add-In, I have to guess at how you implemented sync of calendar items, but I did happen to notice while browsing the data in the Meetings table that the "OUTLOOK_ID" column is null for every single row.

I assume that the add-in is calling into \soap.asmx to do its calls, but I haven't dug through there to trace the code and figure out what is going on.

Could you tell me a little more about how Calendar Sync'ing works? I might be able to troubleshoot this on my own.

No, I have not modified any of the access rights in the Splendid control panel. There are only two users in the system, and they both have full admin rights.

Interestingly, I made a custom view in the Outlook Calendar folder and added the APPID and LastSyncDate as columns and found that all the appointments in Outlook have assigned guids and LastSyncDate data that matches the records in the MEETINGS table in Splendid. If I look at this view while running "Sync Calendar", I notice that all the appointments are written as duplicate rows to the Splendid database, and then the new ID guid of the new duplicate record is overwritten to the APPID field in the outlook appointment object. So I gather from this that for some reason the Add-In can write to the user defined fields but cannot read them (or cannot correctly match them to the existing ids).

At this point I figure either something is munging the ids on the way out of splendid, or my instance of Outlook is screwed up.
I am going to try another instance of outlook and see what I get.