# MS 365 Meeting Sync has Description field type mismatch

**URL:** https://community.spicecrm.io/t/ms-365-meeting-sync-has-description-field-type-mismatch/746
**Category:** Uncategorized
**Created:** [October 20, 2024, 6:32am UTC](https://community.spicecrm.io/t/ms-365-meeting-sync-has-description-field-type-mismatch/746 "2024-10-20T06:32:53Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![processflow](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spicecrm.io/processflow/32/379_2.png) [@processflow](https://community.spicecrm.io/u/processflow)
#### Post date: [October 20, 2024, 6:32am UTC](https://community.spicecrm.io/t/ms-365-meeting-sync-has-description-field-type-mismatch/746/1 "2024-10-20T06:32:53Z")

</div>

MS 365 Meeting Sync has a Description field type mismatch with corresponding SpiceCRM Meeting module mapping (description field)

version: 2024.01.001.1728367438391

steps to reproduce

- sign on with MS 365 single signon on SpiceCRM
- go to MS 365 calendar and create a calendar event and add HTML formatted content in the Description field of the event record (wysiwyg type field)
- go to SpiceCRM calendar and view the meeting - observe the description field showing raw HTML code – as it is text field
- after sync takes place - go back to ms 365 calendar event and now raw html is displayed

SpiceCRM Meeting

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/spicecrm/original/1X/38e29dac94107583ee295fb981f36e0c40d99cdb.png)

0365 Meeting after sync took place

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/spicecrm/original/1X/093a1eaabab57fb33fbdbee16e404101323b51bc.png)

- go to another account in Office 365 that is not synced to SpiceCRM - create calendar event with HTML formatted content – and html formatting remains.

Conclusion: It seems possible that after the 365/SpiceCRM sync takes place, the o365 record is corrupted – and the SpiceCRM Meeting module ‘description’ field is not compatible with the o365 field ???

---

<div class="post-metadata">

### Author: ![maretval](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@maretval](https://community.spicecrm.io/u/maretval)
#### Post date: [October 24, 2024, 4:53pm UTC](https://community.spicecrm.io/t/ms-365-meeting-sync-has-description-field-type-mismatch/746/2 "2024-10-24T16:53:12Z")

</div>

365 Sync seems to pass html only even if the configuration in the table sysmsgraphmappingsegmentitems says otherwise (bodytype = text).  
Customize the fieldset in the CRM and set the meetings.description field to html or Richtext

Set HTML instead of text in bodytype for the sysmsgraphmappingsegmentitems record  
Try out  
Customize the sysmsgraphmappingsegmentitems bodytype record

---

<div class="post-metadata">

### Author: ![processflow](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spicecrm.io/processflow/32/379_2.png) [@processflow](https://community.spicecrm.io/u/processflow)
#### Post date: [October 24, 2024, 5:17pm UTC](https://community.spicecrm.io/t/ms-365-meeting-sync-has-description-field-type-mismatch/746/3 "2024-10-24T17:17:35Z")

</div>

Great - will do.

Is that something that will update in future or would this be a permanent solution?

---

<div class="post-metadata">

### Author: ![maretval](https://avatars.discourse-cdn.com/v4/letter/m/b38774/32.png) [@maretval](https://community.spicecrm.io/u/maretval)
#### Post date: [October 28, 2024, 11:39am UTC](https://community.spicecrm.io/t/ms-365-meeting-sync-has-description-field-type-mismatch/746/4 "2024-10-28T11:39:10Z")

</div>

I can’t answer this question right now. we will discuss that with the team

---

<div class="post-metadata">

### Author: ![processflow](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spicecrm.io/processflow/32/379_2.png) [@processflow](https://community.spicecrm.io/u/processflow)
#### Post date: [October 28, 2024, 12:27pm UTC](https://community.spicecrm.io/t/ms-365-meeting-sync-has-description-field-type-mismatch/746/5 "2024-10-28T12:27:55Z")

</div>

No problem - we will deal with this via the fix you provided and wait patiently for the future updates 🙂
