To be honest, I would regard the what I described above as less than ideal behaviour and it's certainly confusing a lot of our users. Again - this feels like a lot of work for a simple task, and again, is causing usablitiy & adoption issues with our user base. An explicit delete or close action is still required in CRM in order to handle this. cancel meeting button), the meeting is not deleted or cancelled in CRM. If the Meeting Organiser (= appointment owner in CRM) cancels the meeting using normal outlook functionality (e.g. This doesn't sync back to CRM as a dupelicate appointment (thankfully!!), but is still confounding users.Ħ.

A duplicate meeting/appointment is placed in all attendees Dairies (Outlook Calendars) once this notification is sent. The appointment organiser opens up the appointment/meeting in Outlook and distributes it (as per the article above).ĥ. Again - this is less than ideal, but we can live with it.Ĥ. Obviously, and as stated above in your article, no notification email is sent. Outlook synchorinises with CRM for users of the system and places the appointment in their diary (outlook calendar). Create the appointments in CRM and add relevant required attendees (system users)Ģ.

If I may, I would like to get your opinion/feedback on some odd behaviour we are encountering with the Appointment/meeting fucntionality/2-1way synchronisation between OutlookCRM.ġ. Thanks for the article - well documented/nicely articulated and good information to have to hand.

Microsoft outlook private appointment