** AVAILABLE OCTOBER / NOVEMBER 2024 **
Overview
The 'PDF - Set Metadata' action for Power Automate enables PDF document metadata to be updated.
Credit Count
This action consumes 1 credit per operation.
Note, different Encodian actions can consume different number credits. Please always check the action specific documentation and read What is an Encodian Action for a full description of how credits are consumed.
Default Options
The default 'PDF - Set Metadata' flow action parameters are detailed below:
- File Content: A Base64 encoded representation of the PDF file to be processed.
- Author: The author of the document
- Creation Date: The date the document was created
- Keywords: The keywords associated with the document
- Modification Date: The date the document was modified
- Subject: The subject of the document
- Title: The title of the document
** The following values can be reset to a blank value by entering 'clear' as the value: Author, Keywords, Subject and Title
Please refer to the Obtaining the 'File Contents' Parameter article for guidance on how to obtain the 'File Content' parameter ready to provide to an Encodian flow action.
Advanced Parameters
The advanced 'PDF - Set Metadata' flow action parameters are detailed below:
- XMP Metadata: A JSON collection of keypair values to set existing XMP metadata entries on the document provided
- Culture Name: This setting is used to set the culture for processing the request. Please refer to the Culture Names article for a list of supported cultures
Return Parameters
The 'PDF - Set Metadata' flow action returns the following data.
Action Specific Return Values
- File Content - The processed PDF file (Base64)
Standard Return Values
- OperationId - The unique ID assigned to this operation.
- HttpStatusCode - The HTTP Status code for the response.
- HttpStatusMessage - The HTTP Status message for the response.
- Errors - An array of error messages should an error occur.
- Operation Status - Indicates whether the operation has been completed, has been queued or has failed.
0 Comments