Revision Summary Date Revision History Revision Class Comments 5/10/2016 1.0 New Initial Availability 7/14/2016 2.0 Major Significantly changed the technical content. 6/9/2017 3.0 Major Significantly changed the technical content. 3/16/2018 4.0 Significantly changed the technical content.
The DashboardElementsType complex type specifies a collection of DashboardElement elements that describe the elements to be included in a dashboard. The following is the XSD for the DashboardElementsType complex type. <xs:complexType name="DashboardElementsType"> <xs:sequence> <xs:element name="DashboardElement" type="DashboardElementType" minOccurs="0" maxOccurs="unbounded" > </xs:element> </xs:sequence> </xs:complexType> The following table describes the XML elements for the DashboardElementsType complex type. Element Type Description DashboardElement DashboardElementType A collection of complex types that specify the elements for this dashboard. DashboardLayoutsType Complex Type The DashboardLayoutsType complex type specifies a collection of DashboardLayout elements that together describe the layout of a dashboard. The following is the XSD for the DashboardLayoutsType complex type. <xs:complexType name="DashboardLayoutsType"> <xs:sequence> <xs:element name="DashboardLayout" type="DashboardLayoutType" maxOccurs="unbounded" > </xs:element> </xs:sequence> </xs:complexType> The following table describes the XML elements for the DashboardLayoutsType complex type. Element Type Description DashboardLayout DashboardLayoutType A collection of elements that defines the position and area for each element of a dashboard's layout. DataSourceConnectionsType Complex Type The DataSourceConnectionsType complex type specifies a collection of DataSource elements that define external data sources for the dashboard. The following is the XSD for the DataSourceConnectionsType complex type. <xs:complexType name="DataSourceConnectionsType"> <xs:sequence> <xs:element name="DataSource" type="DataSourceType" maxOccurs="unbounded" /> </xs:sequence>
Endpoints The Endpoints HTTP request is used for a client to understand versions are supported by a server and which versions the server no longer supports. The HTTP GET operation is used. The Endpoints request URL is the only URL in this protocol that does not require an endpoint to appear within the URL. All other HTTP URLs in this protocol contain an endpoint encoded into the URL. Usually a protocol user uses this API call first in a session to determine the available endpoints, and then encodes the rest of the API calls with the desired endpoint, selected from among those available as indicated by the return result to this API call. The Endpoints request is not part of the implementation . The HTTP GET request URL is formed as "~/api/endpoints" where the "~" is replaced with the HTTP absolute URI to the report server. For an example, see section . Request Body The request body is There are no parameters. Response Body The response body contains a response in of type Endpoints (see section ). Processing Details There are no special processing details. The request is received by the server and the response is returned. CatalogItemByPath The CatalogItemByPath function is used to request a listing of available catalog items by referencing the path. The HTTP GET operation is used. The following CSDL defines the CatalogItemByPath function. <Function Name="CatalogItemByPath"> <Parameter Name="path" Type="Edm.String" Unicode="false" /> <ReturnType /> </Function> For an example, see section . Request Body The request body is empty. The path parameter appears within the URL, as defined by the CSDL. Response Body The response body contains the requested entity, a Model.CatalogItem item in JSON format (see section .) Processing Details There are no special processing details. The request is received by the server and the response is returned.
A 11 C 11 143 Client and server 91 91 91 91 100 100 91 E Examples 112 116 115 113 112 116 101 F 11 129 120 G 8 H 12 12 I 119 119 10 8 J 129 M Messages 12 N 12 9 O 10 P 119 11 11 142 Protocol Details 91 Protocol examples 112 116 115 113 112 116 101 R References 10 9 11 S Security 119 119 11 T 143 12 12 12 12 V 11 11 X 120