Share via

3.1.4.65 SaveTemporaryAnalyticReport

  • Article

The SaveTemporaryAnalyticReport operation stores a temporary copy of a ReportView complex type (section 2.2.4.160) to the server (2).

The following is the WSDL port type specification of the SaveTemporaryAnalyticReport WSDL operation.

 <wsdl:operation name="SaveTemporaryAnalyticReport" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
   <wsdl:input message="tns:SaveTemporaryAnalyticReportSoapIn"/>
   <wsdl:output message="tns:SaveTemporaryAnalyticReportSoapOut"/>
 </wsdl:operation>

The protocol client sends a SaveTemporaryAnalyticReportSoapIn request message (section 3.1.4.65.1.1), and the server (2) responds with a SaveTemporaryAnalyticReportSoapOut response message (section 3.1.4.65.1.2) as follows:

  • The protocol client MUST send a ReportView.

  • If the server (2) contains a ReportView where all attributes and elements except Location equal those of the passed in ReportView, the server (2) MUST return the GUID of the ReportView on the server (2). The GUID MUST be equal to the RepositoryLocation complex type's (section 2.2.4.161) ItemGuid GUID. The stored ReportView MUST NOT be altered.

  • If the server (2) does not contain a ReportView where all attributes and elements except Location equal those of the passed in ReportView, the server (2) MUST store a copy of the ReportView and MUST return a unique GUID for it. The server (2) MUST replace the Location element for the stored copy which MUST conform to the schema of the RepositoryLocation, such that the ItemType attribute equals TempReportView, as specified in the FirstClassObjectType simple type (section 2.2.5.20), and the ItemGuid attribute equals the returned GUID.

Exceptions:

Error code

Description

InvalidPermission

See Common List of Error Codes (section 2.2.2.1.3).

In case of any other failure, the error code MUST be one of the values specified in section 2.2.2.1.2. A detailed specification of how exceptions are reported by the server (2) is in section 2.2.2.1.