For part 5 of the Dynamics 365 App for Outlook series, we are going focus on specific appointment tracking scenarios. In the following post, we will break down contacts.
Let's get into it…
You cannot track a meeting request. You will receive the message below from the email list view:
Or if you open the meeting invite item, you will see the App is grayed out.
You also cannot track meeting replies (a reply that states someone accepted your meeting request).
However if you accept the meeting request, you can track the appointment only if this was sent from a Non-Dynamics user such as a Contact or an external email. See below:
By default, no. If this was sent from another Dynamics 365 user, you will not be able to track this appointment and you will receive the following message instead of the tracking options. There is a setting that affects how this works. I will be updating this blog post for this scenario specifically in the coming weeks.
When you receive a meeting request from another Dynamics 365 user, if the organizer tracks this into Dynamics before sending, it will show as Track Pending in the recipient's calendar until the async service picks it up.
After the async service picks it up, it shows the following.
If you click the ellipses next to Tracking Failed and select Retry, this will still fail since the Organizer is another user.
If the sending user instead sends the meeting request and then tracks the appointment into Dynamics from their calendar, this issue will not occur. The recipient would instead see the message that "You can't track this meeting because it was organized by another user" message.
There is a setting: TrackAppointmentsFromNonOrganizer, which can be used to track appointments from another Organizer that exists as a Dynamics user. You can update that setting with this tool. Once this is enabled, it will appear with the options to track. Due to some sync issues, I would not enable this until you are on version 220.127.116.116 or higher. For Online instances, this is enabled by default as of 18.104.22.16854.
Let's look at what happens in a scenario where this is enabled. Aaron Richards creates an Appointment from Outlook with WhatsNew Administrator as an attendee but does not track the Appointment. WhatsNew Administrator accepts the Meeting Request and tracks the Appointment to Dynamics from his calendar.
This is the tracked meeting from the WhatsNew Administrator who did not actually create the Appointment, but was now able to track what was created by Aaron because of this setting. Although WhatsNew Administrator tracked the item, the Owner and Organizer are Aaron Richards. The Organizer of the item in Exchange.
Now, if Aaron Richards goes into his Outlook before the next sync cycle and opens the App for Outlook on this Appointment, it will show as Not Tracked
They can click Track and will get this "Scheduling Conflict" message because Dynamics already has an Appointment for these users at this time. The link has not be created with this mailbox yet.
It will go to Track Pending status and after it synchronizes, will show as Tracked.
If you skipped the section above, this requires an Org setting called TrackAppointmentsFromNonOrganizer. Here is an example:
When I create a new appointment in Outlook with required attendees, it sends a meeting request but also creates an appointment on your calendar. When creating an appointment, before I send it (compose mode), I can open the App for Outlook and track it.
After it is sent, the meeting request that exists in your sent items does not actually show as tracked.
But the appointment on your calendar does
This will reflect the changes in Dynamics. If this has meeting recipients, they will also receive an update to the original meeting as you would expect with normal Outlook functionality. You can actually move the dates ahead to a future date or if it is a meeting that already occurred, you can move it backwards. You will want to review the bottom of this post for how we synchronize historical appointments.
It resolves using the method below:
If there are duplicate records within Dynamics 365 with the same email address, the contents of the appointment From field will resolve to the first active record in the following order on an appointment:
a. SystemUser- should always be first b. Contact c. Account d. Lead e. Equipment f. Team g. Business unit h. Email-enabled entities (for example: Queues, custom, etc.)
Appointment recipients will not resolve to inactive User records in the From field. There is a setting that can be changed to resolve to other inactive entity records but this does NOT include inactive Users: ResolveForInactiveEntities. Regardless of this setting, we will not resolve to inactive Users. This is set to False by default.
Here are some additional points on how it resolves recipient email addresses in the To or CC field of an appointment:
If there is an inactive user in the recipients line, the App for Outlook may show that the user matches the email address, but when you track, the promotion will not resolve to that email for the inactive user and it will show up in red as unresolved. It will not resolve to inactive users regardless of the ResolveForInactiveEntities setting.
If the email address is tied to an active user, it will display that in the App for Outlook recipients pane, but it will still resolve to each active Dynamics record with that email address once it is promoted, as long as Set To,cc,bcc fields to unresolved values if multiple matches are found is set to No in System Settings. If this is set to yes, they will show as unresolved. Also, if the ResolveForInactiveEntities setting is True, it will resolve to inactive entity records except inactive Users.
One important thing to mention here is that the emails addresses on the appointment do NOT resolve to records only in the default email address fields within Dynamics. If you have a custom Single Line of Text field with Email format on a Contact record, you may see some interesting results. (Additional screenshots are available in Part 4- working with Emails)
If this appointment is promoted into Dynamics through the Dynamics App for Outlook (as an example), the promoted appointment in Dynamics will show the following values:
To: Bob Jones; BobOpp; BobCase; Leslie Baker; Greg Marcus; Happy Hogan
CC: Bob Jones; BobOpp; BobCase; Leslie Baker; Greg Marcus; Happy Hogan
Yes, you can track a recurring series:
No, you cannot track a single occurrence of a recurring appointment
When you track a recurring appointment, you will see a recurring appointment as well as an appointment record for each occurrence of the recurring series, as seen below:
As mentioned in the last post, if you are familiar with the legacy Outlook client, there was an icon that appeared on tracked items, making it easy to determine if the record was tracked. Unfortunately, with the App for Outlook, there is no icon to show if it is tracked. Additionally, there is no option to pin the App on Appointments. You can see below that the icon to pin the App is missing.
You would need to use Category Tracking, which shows a specified category for Tracked in Dynamics 365. I will not be going into this during this blog series. We may be looking at this in a future post. However, be sure you test this feature thoroughly to ensure it works for your needs.
If you untrack an appointment, you will get the option to untrack or remove the link to the record. If you own the appointment record, you will also get the option to delete the appointment. If you untrack a historical appointment, you will not receive this prompt. It will simply be untracked.
If you untrack a recurring appointment, you will see the following prompt. If you choose Delete, this will only delete future occurrences of the series. The historical occurrences will remain in Dynamics.
This is likely one of the most common questions I encounter.
Appointments in the past: You can still track a past appointment that already exists in Outlook into Dynamics 365, which will create the appointment record in Dynamics, but Dynamics 365 doesn’t synchronize changes on these past appointments or send historical meeting invites.
However, if you are also creating a historical appointment in Outlook prior to tracking into Dynamics, Outlook will still send a meeting request. This will happen with standard Outlook functionality regardless of if the App for Outlook is used or not.
Recurring appointments: In Outlook, a series of appointments can have no end time, but in Dynamics 365, instances as part of the recurring appointment will be created if the instance is either within the near future (12 months), or was modified as an exception of the series.
Service activities and service appointments: You can push service appointments in Dynamics 365 to Outlook as a regular appointment, but the appointment in Outlook won’t sync back to Dynamics 365, and you should always modify the service appointment in Dynamics 365 to provide consistency. Directly updating the appointment in Outlook is not allowed nor recommended.
At the time of this post, this is the most recent functionality
As a reminder, the asynchronous processing can take up to 15 minutes. The processing time of the mailbox items is dependent on the amount of items it has to process, the configuration settings for which items to process, size of attachments, and health of the mailbox.
It is a current design that we have only one appointment form due to the tight integration with the fields required by Exchange and Outlook. This has been brought up many times and there is a Product Enhancement Suggestion here.
Appointment deletions in Dynamics 365
*This does not mean that the user deleting the Appointment must be the owner or organizer. The deletion can be performed through any mechanism/user and a subsequent deletion will only be synchronized to the Exchange mailbox of the user whom previously owned or was the organizer of the deleted appointment.
Also, if a user is an attendee on a tracked Appointment, which they are not the owner or organizer of and this is deleted, they will receive a cancellation in Outlook.
Appointment deletions in Outlook
There is an OrgDbOrgSetting that can change how this works as well. DistinctPhysicalAndLogicalDeletesForExchangeSync, which has a default value of false. If changed to true, the delete logic for synchronization is changed to not delete objects in Exchange unless the object on the Dynamics side is directly deleted by the owning user. This setting will be helpful if you run into a scenario where the Organizer of an Appointment is changed and the original Organizer's mailbox synchronizes before the new Organizer mailbox, the Appointment would be cancelled. See this article. Another scenario where this would be helpful is if you have the "Set To,cc,bcc fields to unresolved values if multiple matches are found" and an item is manually tracked where the Organizer email has multiple matches. This would also send a logical delete.
Stay tuned next week for the rest of this series!
Check out the rest of the series below:
Part 1 | Part 2 | Part 3 | Part 4 | Part 6 | Part 7 | Part 8