PPJ Manual
HomeCurrent IssuesDownloads
  • Welcome
  • Releases
    • PPJ 2023
  • PPJ 2023
  • PPJ Web API
  • PPJ Desktop API
  • Wisej.NET Documentation
  • General
    • Framework
      • Features
        • SAL and SQL Functions
        • Constants and Variables
        • SalContext
        • Visual Toolchest
        • XSal2
        • Reporting Support
        • LINQ Support
        • SalCompileAndEvaluate
        • Unicode Support
        • Startup Arguments
        • App.config
      • Data Types
        • Automatic Casts
        • Dynamic Arrays
      • Controls
        • ToolBar
        • TabControl
        • TableWindow
        • QuickObject
        • Ribbon Bar
        • NavigationBar
      • SQL Support
        • Configuration
        • ADO.NET Drivers
        • Bind and Into Variables
        • DBP Parameters
        • SqlContext
      • Extensions
        • Table Window
        • Unicode Support
        • Bug Fixes
        • Object Oriented Types
        • Custom Parsers
        • Named Properties
        • Microsoft Charts
        • Tabbed MDI
        • Watermark
        • HTML Rendering
      • Skins and Themes
        • Skin Files
        • Theme Files
        • Configuration
        • Skin Editor
        • Theme Builder
      • Tracing
        • Trace Viewer
        • Default Listeners
        • Tracing the Application
      • Spell Checker
        • Dictionaries
    • Ported Application
      • Project Structure
        • Late Bind Calls
        • Visual Styles
        • Unqualified References
        • Message Actions
        • When SQLError
        • Classes
      • Global Items
      • Forms
      • COM/ActiveX
      • Multiple Inheritance
      • Configuration Tool
      • Issues & Workarounds
    • Ported Reports
      • General
      • Crystal Reports
        • Structure
        • Unsupported Features
      • List & Label
        • Report Conversion
        • Structure
        • Document
        • Input Items
        • Passing Data
        • Unsupported Features
      • Reporting Services
        • Features
      • Stimulsoft
        • Break Groups
        • Fields
        • Formulas
        • Cache Mode
Powered by GitBook
On this page

Was this helpful?

  1. General
  2. Ported Reports
  3. List & Label

Input Items

PreviousDocumentNextPassing Data

Last updated 2 years ago

Was this helpful?

The PPJ Framework uses a .NET data set to pass data between the application and reports (for more information about the internal architecture, see ). The data set contains two tables, called InputItems and ReportVariables. All input items and report variables will appear as fields below these two tables in List & Label as shown in the following screenshot:

Field list with Input Items and Report Variables in List & Label

All Report Builder source data types are supported and will be transferred to the target report. Since List & Label has a similar architecture compared to Report Builder, the data set is not filled up front but passed record by record. Reports behave pretty much the same as in the source application and data access is very fast.

In order to extend the report with new fields, open the data set definition (xsd file) and add a field with one of the data types as shown in the following table:

Report data type
.NET data set type

String

String (xs:string)

Number

Decimal (xs:decimal)

Date/Time

DateTime (xs:datetime)

Object

Byte[] (xs:base64binary)

The field can then be added to calls such as Sal.ReportPrint() in the converted application.

List & Label doesn't store data type information about data fields, only the field name is saved in the report. Therefore it is necessary to deploy the data set always with the report. The PPJ Framework uses the xsd file to pass input items and variables properly with the correct data type.

Passing Data