Message-ID: <1577979291.8857.1711664940347.JavaMail.web05$@web05> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8856_2072446912.1711664940347" ------=_Part_8856_2072446912.1711664940347 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
When you save an OfficeWriter report template, the OfficeWriter = Designer encodes it as a custom XML element in a Reporting Services RDL fil= e. The OfficeWriter renderer on the server understands this custom element,= decodes it, regenerates the template, and - using data supplied by Reporti= ng Services - replaces the merge fields or data markers in the template wit= h database values.
=20The RDL files created by the OfficeWriter designer are compliant with th= e Microsoft RDL schema, and can be edited in Microsoft Visual Studio. You c= an edit the generated report in Visual Studio, format tables and text boxes= , and cut-and-paste report definitions from existing reports. You must, how= ever, preserve tables defined in the generated RDL, all custom tags, data s= ource names (query names), and field names.
=20A Table ReportItem is added to the RDL file for each query assigned to t= he template. The structure of an RDL file is:
=20<?XML ...> <Report> <Custom>base64-encoded template</Custom> <DataSources> =09<DataSource> =09=09... =09</DataSource> =09... </DataSources> <DataSets> =09<DataSet Name=3D"DataSet_Query1" > =09=09<Query> =09=09=09<CommandText>Select...</CommandText> =09=09</Query> =09=09<Fields> =09=09=09<Field Name=3D...> =09=09=09 ... =09=09=09</Field> =09=09</Fields> =09</DataSet> =09... </DataSets> <Body> =09<ReportItems> =09=09... =09=09<Table Name=3D"Query1"> =09=09... =09=09</Table> =09</ReportItems> </Body> </Report>=20