Databases Reference
In-Depth Information
To add the EmployeeKey, click the Add button and select “# Employee Key” from the list Fields. Click
OK to close the dialog and the resulting AttributeReference Collection Editor should appear as shown in
Figure 8-29.
Figure 8-29
Click OK to apply the property setting and save the Report Model.
Now that you have seen how to create and manipulate a Report Model, you will look at deploying the
model to the Report Server.
Deploying the Report Model
Report Models are deployed to a central Report Server in much the same way as Reports. The smdl file,
along with the data source, is published via the Reporting Services Web service. Once the Report Model
is published, it can be used by end users.
One slight difference between the deployment of models and reports is the number of folders that are
created. In reports, you deploy to a single target folder. With report models, you can deploy to both a
target Data Source folder and target Model folder. By default, these are simply set to Data Sources and
Models, respectively. To change the target folders, right-click on the Report Model project in the Solution
Explorer and select Properties. From there, you will see properties for the different folder locations as
well as the Overwrite Data Source property and Deployment Server URL.
Once you are ready to deploy the Report Model to the server, click the Build menu and select Deploy
< project name >. Deployment of the model consists of two steps: building the model and sending the
deploy command.
Search WWH ::




Custom Search