1. REST API for Oracle Analytics Publisher in Oracle Analytics Server
  2. Tasks
  3. Manage Reports

Update translation file (XLIFF)

put

/services/rest/v1/reports/{reportPath}/templateFiles/{templateFileName}/xliffs/{locale}

Updates a translation file (XLIFF) associated with a layout definition in the catalog.

Request

Supported Media Types
Path Parameters
  • The locale to assign to the XLIFF (for example, en_US).
  • URL encoded report path. For example, if your report path is "/Sample Lite/Published Reporting/Reports/Balance Letter" then your encoded report path will be "%2FSample%20Lite%2FPublished%20Reporting%2FReports%2FBalance%20Letter". Use double encoded forward slash when you send a REST request to BI Publisher through a load balancer that isn't configured to pass encoded slashes. For example, if your report path is "/Sample Lite/Published Reporting/Reports/Balance Letter" then your encoded report path will be Sample%20Lite%252FPublished%20Reporting%252FReports%252FBalance%20Letter
  • The file name of the layout to which to associate the XLIFF file. For example, employee_listing.rtf.
Body ()
Translation (XLIFF) file
Root Schema : schema
Type: string(binary)
Back to Top

Response

200 Response

Translation file for the specific template in report is updated successfully.
Back to Top

Examples

The following example shows how to update a translation file by submitting a PUT request on the REST resource using cURL.

curl -i \
     --header 'Authorization: Bearer <token>' \
     --header 'Content-Type: application/octet-stream' \
     --request PUT \
     --data-binary @xliffData.xlf \
     'https://hostname/xmlpserver/services/rest/v1/reports/Sample%20Lite%252FPublished%20Reporting%252FReports%252FSales%20Performance+Report/templates/RTFTemplate/xliffs/en_US'

Example of the Response Body

The following example shows the contents of the response body in JSON format.

* Connection #0 to host hostname left intact
Back to Top