web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested Answer

Converting a meeting created in Dynamics into a Teams meeting corrupts formatting

(0) ShareShare
ReportReport
Posted on by 45

We schedule a lot of meetings with clients and prospects through Dynamics 365.  We are now conducting a lot of our meetings over Microsoft Teams, and and are having issues working with Teams meetings in Dynamics 365.  When we convert an appointment that was created in Dynamics to a Teams meeting in Outlook, the Teams info is added to the meeting and we can send the updated invite to the participant, and it will retain the Teams links.  The problem comes when this appointment syncs back to Dynamics, and then subsequently syncs back to Outlook.  Once it Syncs back to Outlook, all of the Teams links are removed from the Appointment in Outlook, and are replaced with some formatting text such as this:

/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
The above text only shows up in Outlook, in Dynamics it just appears blank, but most of the original appointment agenda is missing.
The strange thing is that Outlook and Teams still seem to see this as a Teams meeting, as you still have the option to click the Join Teams Meeting button from the header if you open the Appointment in Outlook, or you can go to your Teams calendar, and the Join link will appear.
Here is some more detail about our environment.
We have enabled Rich Text formatting for the Appointments entity per this article
We have server side email sync turned on and have the Outlook App installed.
We create our appointments via a workflow that sets up the subject and agenda in a specific layout.  We initially create the appointment with no participants, and then once it syncs to the owner's calendar, they open the meeting, check the format of the agenda and make any needed updates (such as adding the Teams links) and then add the participants and sends the meeting invite.
Here is an image of what the appointment looks like once it has synced back to Outlook.
2020_2D00_08_2D00_17_5F00_16_2D00_31_2D00_30.png
I have the same question (0)
  • David Jennaway Profile Picture
    14,065 on at

    I don't think there's an easy solution to this, as I think the problem is that Dynamics 365 is not interpreting the body of the appointment properly, and unfortunately you cannot control which fields are synched

    The best you can probably do is to configure the synchronisation filters so that the appointments are only synched initially from Dynamics 365 to Outlook, but not subsequently synched. Based on your process, you could do this with a filter to only sync appointments with no attendees. However, the problem is that you won't then get the attendee data back into Dynamics 365. You could probably also add a filter to sync appointments after they have happened, to at least get the data into Dynamics 365, and if the appointment has now happened, any corruption of the Teams info in Outlook may not be an issue

  • Bryan Hallas Profile Picture
    45 on at

    Thanks for the response.  I didn't think of using syncronization to keep the appointment to replicate.  I will test this option if I'm not able to resolve the issue another way.  I did some more testing on this, and I tried testing in a non-production environment we have that is just an out of the box install of Dynamics 365.  In the out of the box install with no customization, the appointments symc to Dynamics without any issues, and they show up in Dynamics correctly, including the Join Meeting links.  I haven't been able to determine what in our regular environment might be different.  There are no scripts on the Description field, and I have disabled all of the workflows that trigger on created or modified appointments.

  • Suggested answer
    Bryan Hallas Profile Picture
    45 on at

    I ended up reaching out to Microsoft on this and they were able to find the problem relativly quickly.  As it turns out, the field length on our Appointment Description field had been reset to 2000 charecters.  (I inherited this system, so I don't know why this was done.)

    I expanded the field size to 256,000 charecters and this resolved the issue.  The Teams meetngs now sync to Dynamics correctly and do not get corrupted when they sync back.  

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
iampranjal Profile Picture

iampranjal 51

#2
Martin Dráb Profile Picture

Martin Dráb 39 Most Valuable Professional

#3
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 26 Super User 2025 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans