#CAL EDIT BIN FILE HOW TO#

#CAL EDIT BIN FILE HOW TO#

Thus, it's important to consider how to manage user confusion around converted documents. This can be confusing for users depending on how the host UI user experience is designed. If the user attempts to edit the file again, Office for the web again converts it and creates a second converted file, for example File1.docx. Later, the user returns and opens the original binary file, File.doc, in the Office for the web viewer.Īt this point, the user Might be confused as to why the changes made earlier aren't in the document.The user edits the newly converted document, then ends the editing session.The conversion process starts, and Office for the web calls PutRelativeFile on the host, creating a newly converted file, File.docx.The user clicks the Edit button in the Office for the web viewer.A user opens a binary file named File.doc in the Office for the web viewer.In the basic conversion process, Office for the web creates a new file each time a user attempts to edit a file in a binary file format. Hosts might optionally handle the in-application Edit button themselves by setting the EditModePostMessage property to true and handling the UI_Edit PostMessage. When clicked, this button navigates the user to the HostEditUrl provided for the binary file, which starts the conversion process and eventually redirects the user to the HostEditUrl for the newly converted document. Set the HostEditUrl property to a host URL that runs the convert action when loaded.įollowing these steps ensures that the in-application Edit button displays.Set the UserCanNotWriteRelative property to false (or simply omit it).Hosts must do the following when opening binary documents using the view action: Hosts can support this process in the same way that view -> edit transitions are typically supported. But hosts might wish to open a document first in the Office for the web viewer and use the Office for the web in-application Edit button to convert and edit the document, as is done with documents in editable formats. In the basic conversion flow described earlier, a user runs the convert action using some UI on the host. Office for the web always redirects the topmost window ( window.top).Įnabling convert and edit from within the Office for the web viewer After the document is successfully converted, Office for the web redirects the user to the HostEditUrl that's returned in the PutRelativeFile response.Hosts can then treat these requests differently than other PutRelativeFile requests. Hosts use the X-WOPI-FileConversion header on the PutRelativeFile request to determine that the request is being made in the context of a file conversion.Office for the web sends the converted document back to the host by issuing a PutRelativeFile request against the original file ID.Office for the web retrieves the file from the host and converts it.The host runs the convert action on a binary file.

The conversion process is started byrunning the convert action on the binary file. To support editing binary file formats, hosts must support the PutRelativeFile WOPI operation. The conversion capability is exposed in WOPI discovery as the convert action. Hosts should be aware that users might wish to revert to the previous binary version of the document after it's been converted. Conversion is almost always a lossless process, and there are typically very few, if any, user-visible changes to the layout and formatting of the document during conversion.

Cal edit bin file