office-js

Precondition: Simple Outlook add-in with one (reload case) or two HTML pages (redirect case). Office.initialize called before any objects access Use RoamingSettings object as per documentation: How to save settings in the user's mailbox for Outlook add-ins as roaming settings Coding: // The Office initialize function must be run each time a new page is loaded Office.initialize = function (reason) { $(document).ready(function () { app.initialize(); var settings = Office.context.roamingSettings; // Get the current value of the 'myKey' setting // let's assume it was set and stored with value

Let's say I have in my Outlook Add-In (using Office.js) following code running on a compose form of an appointment: const item = Office.context.mailbox.item; item.loadCustomPropertiesAsync((result) => { const props = result.value; const testProp = props.get("my_prop"); console.log("CUSTOM_PROP", testProp); props.set("my_prop", "test_value"); props.saveAsync((saveResult) => console.log("SAVE_CUSTOM_PROP", saveResult)); }); I see, that it actually is saved on the event. And now a bunch of questions regarding those custom properties: But are those somehow related to extended properties? Are those

The official version of office.js available here: https://appsforoffice.microsoft.com/lib/1/hosted/office.js It contains the following lines in code: window.history.replaceState = null; window.history.pushState = null; This breaks some of the history functionality in my Excel Add-ins (I'm using react and react-router ) Why is office.js nullifying those history functions? I cannot find any explanation in the documentation. The browser control used in Excel does not support History API, if replaceState and pushState were not nulled out they would be available to react but always throw an