As we know, most of business reports are not just based on a static SQL script, they will be varied by different situation such as field column or filter, our RDL element class model allow user to create their own data type and bind the data with our existed report element type. The following is the sample RDL script.

 <?xml version="1.0"?>
 <report name="TestDataBinding" startaction="define_data">
   <reportparameter id="sql.table.name" value="product" />
   <reportaction name="define_data" nextaction="generate_sql">
      <dataitemset id="sql.fields">
         <sqlfield id="sql.fields.1" field="category_name" alias="cat" />
         <sqlfield id="sql.fields.2" 

… Continue Reading

Inside the last post, I introduced how RDL deal with procedural flow and macro variables, the following is another sample that illuminates how RDL handle the report layout.

 <?xml version=”1.0″?>
 <report name=”TestReportItemlayout” startaction=”format_report” librarydir=”E:\reporttools\src\Aspose\ReportTools\ReportTools.RDLElement\bin\Debug”>
   <reportaction name=”format_report”>
      <log message=”format report!” level=”Debug” />
      <reportparameter name=”body.top” value=”5″ />
      <reportparameter name=”body.left” value=”5″ />
      <reportparameter name=”row.height” value=”10″ />
      <reportparameter name=”column.width” value=”50″ />
      <reportparameter name=”header.height” value=”25″ />
      <reportparameter name=”footer.height” value=”30″ />
      <reportparameter name=”body.column.count” value=”0″ />


      <reportitem left=”${body.left}” top=”${body.top}” label=”mainpage”>
         <reportitem height=”${header.height}” label=”header”>
            <reportitem left=”${int::parse(column.width) * rdl::get-zindex()}” 

… Continue Reading