Release notes for apps for Office (Office 2013 SP1, office.js v1.1, schema v1.1)
Find information about known issues for developing an app for Office using Office 2013 SP1, office.js version 1.1 and apps for Office manifests schema version 1.1.
Last modified: April 10, 2014
Applies to: Access app for SharePoint | Excel 2013 | Excel 2013 SP1 | Excel Online | Exchange Online | Exchange Server 2013 SP1 | Outlook 2013 SP1 | Outlook Web App | OWA for Devices | PowerPoint 2013 | PowerPoint 2013 SP1 | PowerPoint Online | Project 2013 SP1 | Project Professional 2013 | Word 2013 | Word 2013 SP1
Apps for Office manifests schema: v1.1
Mail apps supported in compose forms
Attachment support in mail apps
In this release, all the Outlook clients (the Outlook rich client, Outlook Web App and OWA for Devices), Exchange Server and Exchange Online support getting item attachments to server-side code using callback tokens. For more information, see How to: Get attachments of an Outlook item from an Exchange server.
Parity between Outlook clients
Adding a binding to a named content control in Word may fail
In Word, if there are content controls in both the main document and a subdocument (for example, textbox, header, footer), or in multiple subdocuments, attempting to use the Bindings.addFromNamedItemAsync method to bind to another control in that document may fail as if there was a name collision.
Reading table data as a "text" coercion type may return unexpected characters past the null terminator
In Word, if you use the Document.getSelectedDataAsync method to read the selected data from a table and specify the "text" coercion type, you should ignore the characters after the null-terminator in the returned data, if it's present.
Partial writing to a table may fail
If you are doing partial writing to tables, don’t include header data to get the best results. Because of a known issue, partial writing by calling the Binding.setDataAsync method with the "table" coercion type may fail if the operation includes the last row of the table. To work around this, specify null for the header array in the TableData object that is passed to the data parameter in the setDataAsync method call.
Writing to a table may fail
If you are doing full writing to tables, include header data to get the best results. Because of a known issue, partial reading using the Binding.getDataAsync method or writing by calling the Binding.setDataAsync method with the "table" coercion type may not set all the rows of the table correctly if the header row is null. To work around this, specify data for the header array in the TableData object that is passed as an argument to the setDataAsync method.