Delete Point of View

Deletes the data associated with a point of view from the calculation cube.

This is an asynchronous call, so use the job status URI to determine whether the operation is complete.

This API is version v3.

Required Roles

Service Administrators

REST Resource

POST /HyperionPlanning/rest/v3/applications/{AppName}/jobs/

Note:

Before using the REST resources, you must understand how to access the REST resources and other important concepts. See Implementation Best Practices for EPM Cloud REST APIs. Using this REST API requires prerequisites. See Prerequisites.

Request

Supported Media Types: application/json

The following table summarizes the client request parameters specific to this job.

Table 23-10 Parameters

Name	Description	Type	Required	Default
jobType	Delete POV	Payload	Yes	None
jobName	Name of the job Example: "Delete POV"	Payload	Yes	None
povDelimiter	Delimiter used in POV values. The delimiter must be enclosed in double quotation marks. Other than a comma, only these delimiters are supported: _ (under score) # (hash) & (ampersand) ~ (tilde) % (percentage) ; (semicolon) : (colon) - (dash) Example: "povDelimiter":":" Note: When submitting multiple POVs for calculation, do not use a comma as the delimiter to separate POV members. Comma is reserved for separating POV groups as shown in this example: FY21:Jan:Actual:Working,FY21:Feb:Actual:Working,FY21:Mar:Actual:Working	Payload	Yes	:: (Double Colon)
povName	Name of the POV to delete Example: "povName":"FY21:Jan:Actual:Working"	Payload	Yes	None

Sample Payload

{
   "jobType":"Delete POV",
   "jobName":"Delete POV",
   "parameters":{
        "povDelimiter":":",
        "povName":"FY21:Jan:Actual:Working"
   }
}

Response

Supported Media Types: application/json

Table 23-11 Parameters

Name	Description
jobId	ID of the job that is created
jobName	Name of the job
details	In case of errors, details are published with the error string
status	See Migration Status Codes.
links	Detailed information about the link
href	Links to the API call
action	HTTP call type
rel	Can be self and/or Job-details. If set to Job Status, you can use the href to get the status of the job.
data	Parameters as key value pairs passed in the request

Example of Response Body

The following examples show the contents of the response body in JSON format:

Example 1: Job is in Progress

{
    "jobId": 26,
    "jobName": "Delete POV",
    "status": -1,
    "descriptiveStatus": "Processing",
    "details": null,
    "links": [
        {
            "href": "http://<BASE-URL>/HyperionPlanning/rest/v3/applications/BksML40/jobs/26",
            "action": "GET",
            "rel": "self",
        },
        {
            "href": "http://<BASE-URL>/HyperionPlanning/rest/v3/applications/BksML40/jobs/26/details",
",
            "action": "GET",
            "rel": "job-details "
        }
    ]
}

Example 2: Job Status with No Errors

{
    "jobId": 26,
    "jobName": " Delete POV",
    "status": 0,
    "descriptiveStatus": "Success",
    "details": null
    "links": [
        {
            "rel": "self"
            "href": "http://<BASE-URL>/HyperionPlanning/rest/v3/applications/jobs/26",
            "action": "GET",
        },
 {
            "rel": "job-details"
            "href": "http://<BASE-URL>/HyperionPlanning/rest/v3/applications/jobs/26/details",
            "action": "GET",
        }

    ]
}