Overview
This web service cannot append history. It replaces the entire resource history for a single resource. A new set of history records (PwsResourceHistory) for the specified resource (PwsResourceRef) are supplied. The If you want to add a new history row you could PwsGetResouce which retrieves all their current history. You can then copy that data structure, append an additional history row, and resubmit using this web service.
The service returns the identity of the resource (PwsResourceRef) that has been updated.
...
Element | Data Type | Required? | Default | Description | Sample Data |
---|---|---|---|---|---|
Int32 | No | Click here for more information. | 1 | ||
String | Yes | Click here for more information. | AaJ0FpWv/5xR3lRe/9G87g== | ||
History | Yes | The resource history records. All existing history will be replaced by the history supplied here. | |||
ResourceIdentity | Yes | The resource identity. | |||
ResourceTimestamp | String | No | This is a Base64 encoded timestamp optionally utilized for resource locking. | ||
SetNullValuesFromResourceTypeFlag | Boolean | No | falseIf set to 'true', resource attributes that are currently set to null will take on the values associated with the assigned resource type | This is used to determine whether or not to apply resource type defaults on creation of a history row. If you pass 'True' we use the defaults. If you pass 'False' we assume the following:
These settings can be overridden on a per history row basis by specifying another value. | false |
Request Usage Example(s)
...