DeleteCalendarValues request message
- Last UpdatedSep 11, 2023
- 1 minute read
Example request
This is an example of the full structure of a DeleteCalendarValues request.
<DeleteCalendarValueRequest>
<Credentials>
<Username>User</Username>
<Password>********</Password>
<Session />
</Credentials>
<Value>
<Name>ConveyorRate</Name>
<StartDateTime>2014-10-01T00:00:00</StartDateTime>
</Value>
</DeleteCalendarValueRequest>
Request parameters: Credentials section
The Credentials section contains the security details for authentication. You can provide the Username and Password values to use the Basic security method. If you do not provide explicit security values, Web services will attempt to use Integrated authentication. You must provide either Basic credentials, Integrated credentials, or a Session ID.
<Credentials>
<Username>User</Username>
<Password>********</Password>
<Session />
</Credentials>
|
Parameter |
Description |
|---|---|
|
Username |
The login name of the AVEVA™ Production Management user. This is a string value. Username and Password together are mutually exclusive with Session. |
|
Password |
The password that is associated with the AVEVA Production Management user. This is a string value. Username and Password together are mutually exclusive with Session. |
|
Session |
A GUID string value that identifies the session. This is a string value. Mutually exclusive with Username and Password. |
Request parameters: Value section
The Value section holds a set of values to pass in the request.
<Value>
<Name>ConveyorRate</Name>
<StartDateTime>2022-01-22T00:00:00</StartDateTime>
</Value>
|
Parameter |
Description |
|---|---|
|
Name |
(Required) The name of the calendar key to delete. This is a string value. For example, ConveyorRate. |
|
StartDateTime |
(Required) The StartDateTime of the calendar key. For example, 2022-01-22T18:00:00Z. |