In new outlook desktop , office.js doesn't contain the field "dateTimeSent" for mail. However it's available in Office on the web. about office-js

[anjalitp]

The Office.context.mailbox.initialData is not designed for public use. It's an internal attribute, and your add-in should not depend on it. Officially supported date properties provided by our API are:

• Office.context.mailbox.item.dateTimeCreated
• Office.context.mailbox.item.dateTimeModified

[sachidanand-cloudextend]

Hi Team,
Thanks for the response.
But dateTimeCreated and dateTimeModified isn't the correct property to use, when I have saved the mail as draft for sometime and send later.

Let's say , I have saved a mail as draft and kept it for one month , after one month when I send the mail, dateTimeCreated will be one month ago, but dateTimeSent would be today, so dateTimeCreated doesn't give us the correct date when mail was sent.

For example: Today I saved a mail as draft and sent it after sometime. Here is the response from graph api.
Please have a look at the properties createdDateTime and sentDateTime

[anjalitp]

@sachidanand-cloudextend Currently, there isn't a direct API to retrieve the dateTimeSent property. However, you can utilize the Office.context.mailbox.makeEwsRequestAsync API as a workaround to obtain this information. Please refer the documentation for more details on this API.

Also, we track Outlook add-in feature requests on our Tech Community Page. Please submit your request there and choose the appropriate label(s). Feature requests on Tech Community are considered, when we go through our planning process.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it is marked as needing author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for your interest in Office Add-ins!

[microsoft-github-policy-service]

This issue has been closed due to inactivity. Please comment if you still need assistance and we'll re-open the issue.