ReportExecutionService.LoadReportDefinition Method (Byte[], Warning )
Applies To: SQL Server 2016 Preview
Creates a report execution from a report definition supplied by the client.
Namespace: ReportExecution2005
Assembly: ReportExecution2005 (in ReportExecution2005.dll)
Syntax
public ExecutionInfo LoadReportDefinition(
byte[] Definition,
out Warning[] warnings
)
public:
ExecutionInfo^ LoadReportDefinition(
array<unsigned char>^ Definition,
[OutAttribute] array<Warning^>^% warnings
)
member LoadReportDefinition :
Definition:byte[] *
warnings:Warning[] byref -> ExecutionInfo
Public Function LoadReportDefinition (
Definition As Byte(),
<OutAttribute> ByRef warnings As Warning()
) As ExecutionInfo
Parameters
Definition
Type: System.Byte[]A byte stream containing the Report Definition Language (RDL) for the report.
warnings
Type: ReportExecution2005.Warning[]A collection of Warning objects containing warnings that may have occurred during report publishing.
Return Value
Type: ReportExecution2005.ExecutionInfo
An ExecutionInfo object containing information for the report execution.
Remarks
The table below shows header and permissions information on this operation.
SOAP Header Usage |
(Out) ExecutionHeaderValue (Out) ServerInfoHeaderValue |
Native Mode Required Permissions |
ReadProperties on all subreports AND ExecuteReportDefinition (System) |
SharePoint Mode Required Permissions |
ViewListItems on all subreports AND UseRemoteAPIs |
This method should be called prior to calling the Render method for a report.
The returned report execution will need to be processed before it is rendered. A new execution is created and the ExecutionInfo is returned with a new ExecutionID value.
Reports instantiated with the LoadReportDefinition method are temporary. They are not represented in the report server namespace, and are discarded when the server session expires.
Reports instantiated with the LoadReportDefinition method are not securable, and may not be shared with other users; the person who created the execution with LoadReportDefinition is the only user who may access them.
Subreports and data source references with relative paths are not supported using this method. However, absolute paths to catalog items can be used.
Examples
Legacy Code Example
Please see Render for an example.
See Also
ReportExecutionService Class
ReportExecution2005 Namespace
Return to top