1. User's Guide
  2. Providing For Detailed Data and Documents in Reports
  3. Attaching Cell Documents in a Report
  4. About Attaching Cell Documents in a Report

About Attaching Cell Documents in a Report

Cell documents that are attached at the data source can be accessed in reports. The attached documents appear as hyperlinks at the end of a PDF or snapshot report. The documents are accessed in the HTML client when drilling into a cell. In addition, you can insert footnotes into a text object or text cell of the report that lists information about the attached cell documents by selecting the ListofCellDocuments text function. All cell documents have a point of view associated with the data cell to which they are attached.

A data cell can contain multiple cell documents. If a data cell contains cell documents in the data source, a designer can extract those documents, based on the given cell’s POV. Cell documents can be attached to reports contained in books and snapshot books.

To attach cell documents:

  1. Select a data type cell in a grid.
  2. In Cell Properties, select Retrieve Cell Documents.

    For optimum retrieval performance, select Retrieve Cell Documents only for cells with attachments to include in the report. If cell documents exist for the selected cell, they are appended to the report when printed.

When you attach cell documents in a report, consider the following points:

  • Include the correct supported extensions for files.

  • Files which are corrupt or improperly uploaded to the ADM provider will not print.

  • Documents containing file extensions that are not properly registered to print will fail.

  • Oracle Hyperion Financial Reporting Web Studio does not support Microsoft files containing macros or that trigger UI components requiring user input. Some Microsoft files with macros perform operations when the file is opened which include the launching of dialogs requiring user input. Files that display dialogs or UI components requiring user input may not be available to print.

    This may also hold up the completion of the PDF generation process. The server’s administrator may need to stop the application through Task Manager to resume printing activities. Because the application is launched under the SYSTEM account, it may not be visible since the process was not initiated by the login account.