![inserting tables in outlook for mac inserting tables in outlook for mac](https://support.content.office.net/en-us/media/990d150d-00db-4cab-9f07-f18c10c3eb8b.png)
Your mail add-in can get the CustomProperties MAPI-based extended property by using the EWS GetItem operation. (For more information about this object, see MS-OXCEXT 2.2.5 Mail App Custom Properties.) You can then use EWS or REST to get this MAPI-based property. The following is an example of the structure, assuming there are three defined roaming settings named add-in_setting_name_0, add-in_setting_name_1, and add-in_setting_name_2. The data in a RoamingSettings object is stored as a serialized JavaScript Object Notation (JSON) string. You should explicitly save all the roaming settings after updating them so that they will be available the next time the user opens your add-in, on the same or any other supported device. Your mail add-in can access roaming settings when it roams on any device it's designed to run on (desktop, tablet, or smartphone).Ĭhanges to this data are stored on an in-memory copy of those settings for the current Outlook session. Examples of such data include the user's personal data and preferences. You can specify data specific to a user's Exchange mailbox using the RoamingSettings object. Custom data per mailbox: roaming settings The data is stored on the server for that mailbox, and is accessible in subsequent Outlook sessions on all the form factors that the add-in supports. That is, the data stored through roaming settings is not accessible by custom properties, and vice versa. Custom properties, which manage custom data for an item in a user's mailbox.īoth of these give access to custom data that is only accessible by your Outlook add-in, but each method stores the data separately from the other.Roaming settings, which manage custom data for a user's mailbox.You can manage custom data in your Outlook add-in by using either of the following: