ReportingService2010.GenerateModel Method (String, String, String, Property, Warning)
Applies To: SQL Server 2016 Preview
Generates a default model on top of a shared data source.
Assembly: ReportService2010 (in ReportService2010.dll)
[<SoapDocumentMethodAttribute("http://schemas.microsoft.com/sqlserver/reporting/2010/03/01/ReportServer/GenerateModel", 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 GenerateModel : DataSource:string * Model:string * Parent:string * Properties:Property * Warnings:Warning byref -> CatalogItem
The fully qualified URL of the data source including the file name and .rsds file name extension.
The name of the model to create.
The fully qualified URL for the parent folder that will contain the model.
XML that defines properties to set on the model and values to set them to.
The top-level element is Properties.
The table below shows header and permissions information on this operation.
SOAP Header Usage
Native Mode Required Permissions
SharePoint Mode Required Permissions
The report server sets the IsGenerated property on the generated model when GenerateModel is called.
Models are generated by using the credentials specified in the shared data source. As a result, two different users can generate different models from the same data source. Note that when a shared data source is configured to store credentials in the report server, GenerateModel always impersonates the user whose credentials are stored, even if the shared data source is configured to impersonate the currently authenticated user.
When the model is created, the default model item security is applied to the nodes in the model.
When the model definition is generated, custom properties stored in the model definition are propagated as custom properties on the model item in the folder namespace, and new custom property values overwrite existing custom property values.