Microsoft Office Integration

From Grooper Wiki
Jump to navigation Jump to search

2.9

This piece of functionality has undergone drastic changes since writing this article and the information may be outdated or inaccurate as of now.
Native text for Microsoft Office applications is a powerful data integration tool in Grooper.

Easier access to the contents of files from the worlds most used business application suite.

About

Microsoft Office integration allows a Grooper user to leverage the native text of files generated in the Microsoft Office Suite such as Microsoft Word documents and Microsoft Excel spreadsheets. This feature can pull the native text from and perform type-specific activities on these files.

Supported File Types

  • Microsoft Word documents (.docx)
  • Microsoft Excel spreadsheets (.xlsx)

How to Use

To make use of this feature, ensure that Microsoft Office is installed on the machine running Grooper Design Studio.

Getting a Result

  1. In Grooper Design Studio select a Batch that contains the desired documents.
  2. Select the document whose native text you wish to view.
  3. Use the object command Excel Document > Excel to CSV....
    • The Excel to CSV command will add a child document object for each page in the native file.
    • The Open command will literally open the file in whatever the native application is.
    • The Save As command will simply let you save the file to somewhere in your file system out of Grooper.
  4. In the subsequent Excel to CSV window that opens up, choose a Conversion Method.
    • Burst will convert the Excel file to a CSV and saves the results as child object(s).
    • SaveNew will convert the Excel file to a CSV and save the result as a new file.
    • Convert will convert the native Excel file to a CSV and replace the native file.
Microsoft office integration 001.png


Version Differences

Prior to Grooper 2.9 files from the Microsoft Office Suite had to be rendered (essentially a "print...") to PDF in order to view contents and use activities more effectively.