Outlook: Message body is removed from saved draft email about office-js

[MrDaleQ]

@exextoc is there any update on this issue?

We are seeing this reported by an increasing number of customers and now have replicatable instances of the issue.

[ndeleuze]

@MrDaleQ would you be able to provide more information about your add-in? The manifest and source code would help us investigate the issue and determine if your add-in is the cause. If this is the case, then the code that runs during the OnMessageCompose event would most likely be the culprit.

[MrDaleQ]

Hi @ndeleuze, thanks for replying here.

The addin manifest can be pulled from outlook.signature365.com/manifest.xml

The add-in itself has been in production for a number of years now, and this issue did not appear until the start of Feb '24 - from my understanding with the dev team, no changes have been made to the OnmessageCompose code recently.

@barclayadam are you able to add anything here?

[ndeleuze]

@MrDaleQ it looks to me from your manifest that you are not subscribing to the OnMessageCompose event, only OnNewMessageCompose. Would you be able to provide some of the launch event code from your Add-in and/or describe the functionality of your Add-in?

[barclayadam]

@ndeleuze Hi, I'm the lead developer of the above mentioned add-in.

You are correct, the add-in only subscribes to OnNewMessageCompose. We have been using that since the first set of events were released and have not investigated adding / changing to the OnMessageCompose event yet.

Our add-in provides signature management, using the built-in setSignatureAsync Office API.

Regardless of the events we use, we do not modify the email body. We use setSignatureAsync to insert the signature (plus adding inline attachments as base64).

In a very few specific instances, with our task pane open and when changing the From address we do small adjustments to fix duplicate newlines inserted by Outlook (which may no longer be needed), but that is not what we are seeing here.

[MrDaleQ]

@ndeleuze please see the update from adam above

[MrDaleQ]

@ndeleuze Kwame is currently speaking to one of our customers that is experiencing this issue. I will update as / when I hear back.