ReportingService2010.SetSubscriptionProperties Method (String, ExtensionSettings, String, String, String, ParameterValue)
Sets the properties of a subscription.
Assembly: ReportService2010 (in ReportService2010.dll)
[<SoapDocumentMethodAttribute("http://schemas.microsoft.com/sqlserver/reporting/2010/03/01/ReportServer/SetSubscriptionProperties", RequestNamespace = "http://schemas.microsoft.com/sqlserver/reporting/2010/03/01/ReportServer", ResponseNamespace = "http://schemas.microsoft.com/sqlserver/reporting/2010/03/01/ReportServer", Use = SoapBindingUse.Literal, ParameterStyle = SoapParameterStyle.Wrapped)>] [<SoapHeaderAttribute("ServerInfoHeaderValue", Direction = SoapHeaderDirection.Out)>] [<SoapHeaderAttribute("TrustedUserHeaderValue")>] member SetSubscriptionProperties : SubscriptionID:string * ExtensionSettings:ExtensionSettings * Description:string * EventType:string * MatchData:string * Parameters:ParameterValue -> unit
The ID of the subscription.
An ExtensionSettings object that contains a list of settings that are specific to the delivery extension.
A meaningful description that is displayed to users.
The type of event that triggers the subscription.
The data that is associated with the specified type of event. This data is used by an event processing extension to match the subscription with an event that has fired.
The table below shows header and permissions information on this operation.
SOAP Header Usage
Native Mode Required Permissions
SharePoint Mode Required Permissions
The value of the EventType parameter must correspond to an event processing extension that is configured on the report server. If the event type is not handled by an event processing extension, a SOAP exception is thrown with the error code rsInvalidEvent. The event type must be handled by an event processing extension that creates notifications. When a value for the EventType parameter is received, the event processing extension is queried to determine whether the event creates notifications. If it does not, a SOAP exception is thrown with the error code rsEventNonSubscribeable.
The value of the MatchData parameter depends on the event type. If the event is a TimedSubscription event, a ScheduleDefinition object is required as the MatchData parameter. You must first serialize the ScheduleDefinition object as XML in order to pass it as a string value and create a subscription based on the schedule. The XML structure might resemble the one in the following example:
<ScheduleDefinition> <WeeklyRecurrence> <StartDateTime>2003-02-24T09:00:00-08:00</StartDateTime> <WeeksInterval>1</WeeksInterval> <DaysOfWeek> <Monday>True</Monday> </DaysOfWeek> </WeeklyRecurrence> </ScheduleDefinition>
The value of the StartDateTime element when it is passed as an XML string should correspond to the date format ISO 8601. This international date and time standard is the extended format CCYY-MM-DDThh:mm:ss+/-Z where "CC" represents the century, "YY" the year, "MM" the month and "DD" the day. The letter "T" is the date and time separator and "hh", "mm", "ss" represent hour, minute and second respectively. This representation can be immediately followed by a "Z" to indicate Coordinated Universal Time (UTC). To indicate the time zone, represented as the difference between the local time and Coordinated Universal Time, "Z" is preceded by a "+" or "-" sign, followed by the difference from UTC represented as hh:mm.
If the schedule definition for a TimedSubscription is a shared schedule, you must pass the schedule ID of the shared schedule as the MatchData parameter. The schedule ID is passed as a String, for example, "4608ac1b-fc75-4149-9e15-5a8b5781b843". The schedule ID can be obtained by calling the ListSchedules method.
If the event is a snapshot update subscription, set MatchData parameter to null (Nothing in Visual Basic).
A SharePoint non-administrative user’s ‘Work e-mail’ property in their SharePoint User Information should be the TO e-mail delivery extension setting