Not sure why that specific feature has been effected by the update to OS Mojave, but it is quite irritating and really hampers our productivity. Have not heard back from them as of today. After taking control of my screen and going through their procedures, their only advice to me was to uninstall and reinstall Microsoft Office and/or to uninstall OS Mojave and reinstall the previous version of OS that worked with mail merge documents. I chatted with Microsoft Tech Support the day of the update, and they could not figure out the problem either. Documents can be opened by removing all merge data and header info, but cannot be used as or made into mail merge documents. A second after launching the operation to start the list conversion a "Microsoft Error Reporting" window pops up indicating that the XML Converter (list in Microsoft Excel on same HDD) malfunctioned. Restart Content Server and Inbound Refinery.After updating to OS Mojave, Microsoft Word (v16.18) cannot open any Mail Merge documents or perform a new Mail Merge (setting up a new form document, "Use Existing List"). When finished, click Close to close the File Formats page and then close the Configuration Manager. Repeat steps 5 through 8 for all Microsoft Office formats you want to convert to HTML. For example, for application/msword, you would select the conversion option Word HTML. Select the HTML conversion option from the Conversion list appropriate to the Office document format you selected. The Edit File Format dialog box is displayed. For example, for Microsoft Word, you would select application/msword.Ĭlick Edit. Select the application format for the Office document type you want to convert from the Format column. Select File Formats from the Options menu. The Configuration Manager applet is started. The Administration Applets for page is displayed.Ĭlick Configuration Manager. In the navigation menu, select Adminstration, Admin Applets. To make changes, complete the following steps: The Primary Web Rendition page is displayed.Įnable Convert selected MS Office formats to MS HTML.įile formats and conversion methods for Inbound Refinery can be managed in Content Server using the Configuration Manager. In the navigation menu, select Conversion Settings and then Primary Web Rendition. Make sure you are logged into the Inbound Refinery as an administrator. The Conversion column lists the appropriate conversion option according to the file type. Select the Microsoft Office document file types you want to convert to HTML. The File Formats Wizard for page is displayed. In the navigation menu, select Administration, Refinery Administration and File Formats Wizard. Make sure you are logged into Content Server as an administrator. Information on setting these mappings is covered in the following sections:įile formats and conversion methods for Inbound Refinery can be managed in Content Server using the File Formats Wizard. The Configuration Manager applet gives you greater control over which file extenstions are mapped to which conversion options. They can be set either using the File Formats Wizard or the Configuration Manager applet. The added conversion options for HTML Conversion are not automatically mapped: they must be mapped manually. Installing and enabling the MSOfficeHtmlConverterSupport component on a content server adds four HTML conversion options on the File Formats Wizard page:įor a Microsoft Office document to be processed by Inbound Refinery, its file extension must be mapped to a format name that is associated with the HTML Conversion method. This service extracts the HTML page of the ZIP file to /groups/ dSecurityGroup/documents//~extract/~~cachedrendition/~.htm, and displays it in the browser.ħ.2.1 Configuring Content Servers to Send Jobs for HTML Conversionįile formats and conversion methods are used in Content Server to define how content items should be handled by Inbound Refinery and the conversion options. When a user clicks on the web-viewable link in Content Server of a document converted to multiple HTML pages by Inbound Refinery, the HCSP page redirects the server to the Content Server DISPLAY_HTML_PACKAGE service. Optionally, a thumbnail rendition of the native Microsoft Office file If conversion results in multiple HTML pages, the following files are returned to Content Server:Īn HCSP page as the primary web-viewable renditionĪ ZIP file that includes the HTML output from the Office application If a single HTML page is returned to Content Server, it is used as the web-viewable file. Inbound Refinery automates the process of converting the files to HTML using the native Microsoft Office applications. When HTML Converter is enabled to work with Inbound Refinery, native Microsoft Office files checked into Content Server are sent to Inbound Refinery for conversion.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |