Save Splitted Report Document To File Collection
- 24 Apr 2025
- 1 Minute to read
- DarkLight
Save Splitted Report Document To File Collection
- Updated on 24 Apr 2025
- 1 Minute to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback!
General
This type of action can be used to splitted parts of a previously created report document to a previously created File Collection.
Example: Let's suppose you have created a report document using a Create Report Document Action which results in a PDF file with 5 pages. If you want to save each of these pages individually to a File Collection, you can use this action.
The following table shows which file types are supported to be splitted and how they will be splitted:
File Type | Description |
|---|---|
| Adobe PDF Document | Splitted by page. |
| Microsoft Excel Workbook | Splitted by worksheet. |
| Microsoft PowerPoint Presentation | Splitted by slide. |
| Microsoft Word Document | Splitted by page. |
Properties
This type of action has the following properties:
Name | Description |
|---|---|
| Report Document | The report document that shall be splitted and saved to the File Collection. |
| File Collection | The File Collection to which the splitted Report Document will be saved to. |
| Target File Type | The file type in which to save individual splitted parts to the File Collection. The available file types depend on the file type of the splitted report document. |
| DPI | The DPI in which to render the individual part images. This property is only available if the property Target File Type is set to an image file type. |
| Output Path | An Expression that returns a string that contains the output path for individual files (see below). The file type extension does not have to be returned by the expression, because Mail & Deploy will add it automatically based on the selected Target File Type. Mail & Deploy will automatically create required sub-directories. |
Output Path Expression
Within the Expression of the Output Path property an additional parameter PageNumber is available that contains the page number of the processed part.
Example
Let's supposed you have the following expression:
Mail & Deploy Expression
"Report_Page_" & [PageNumber]
This would lead to the first page to be exported to Report_Page_1, the second page to Report_Page_2 etc.
Was this article helpful?