Export (0) Print
Expand All
Expand Minimize
This topic has not yet been rated - Rate this topic

ReportingService2010.GenerateModel Method

Generates a default model on top of a shared data source.

Namespace:  ReportService2010
Assembly:  ReportService2010 (in ReportService2010.dll)
public function GenerateModel(
	DataSource : String, 
	Model : String, 
	Parent : String, 
	Properties : Property[], 
	Warnings : Warning[]
) : CatalogItem

Parameters

DataSource
Type: System.String
The fully qualified URL of the data source including the file name and .rsds file name extension.
Model
Type: System.String
The name of the model to create.
Parent
Type: System.String
The fully qualified URL for the parent folder that will contain the model.
Properties
Type: ReportService2010.Property[]
XML that defines properties to set on the model and values to set them to.The top-level element is Properties.
Warnings
Type: ReportService2010.Warning[]
[out] An array of Warning objects which describe any warnings that may have occurred during the generation of the model. The top-level element is Warning.

Return Value

Type: ReportService2010.CatalogItem
A CatalogItem object for the newly created model.

The table below shows header and permissions information on this operation.

SOAP Header Usage

(In) TrustedUserHeaderValue

(Out) ServerInfoHeaderValue

Native Mode Required Permissions

ReadProperties on DataSource AND CreateModel on Parent

SharePoint Mode Required Permissions

AddListItems on Parent AND ViewListItems on DataSource

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.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.