Jump to

• Request
• Response

Delete a goal metric detail record

delete

/crmRestApi/resources/11.13.18.05/goals/{GoalNumber}/child/GoalMetrics/{GoalMetricsUniqID}/child/GoalMetricDetails/{GoalMetricDetailsUniqID}

Request

Path Parameters

• GoalMetricDetailsUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- GoalId, TargetStartDate, TargetEndDate, ResourceId and KPICategoryName ---for the Goal Metric Detail resource and used to uniquely identify an instance of Goal Metric Detail. The client should not generate the hash key value. Instead, the client should query on the Goal Metric Detail collection resource with a filter on the primary key values in order to navigate to a specific instance of Goal Metric Detail.
  
  For example: GoalMetricDetails?q=GoalId=<value1>;TargetStartDate=<value2>;TargetEndDate=<value3>;ResourceId=<value4>;KPICategoryName=<value5>
• GoalMetricsUniqID(required): string
  This is the hash key of the attributes which make up the composite key--- GoalId, ResourceId, TargetStartDate and TargetEndDate ---for the Goal Metric resource and used to uniquely identify an instance of Goal Metric. The client should not generate the hash key value. Instead, the client should query on the Goal Metric collection resource with a filter on the primary key values in order to navigate to a specific instance of Goal Metric.
  
  For example: GoalMetrics?q=GoalId=<value1>;ResourceId=<value2>;TargetStartDate=<value3>;TargetEndDate=<value4>
• GoalNumber(required): string
  The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=

Header Parameters

• Metadata-Context:
  If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
• REST-Framework-Version:
  The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Default Response

No Content. This task does not return elements in the response body.

Back to Top