# Input Items

The PPJ Framework uses a .NET data set to pass data between the application and reports (for more information about the internal architecture, see [Passing Data](/general/ported-reports/list-and-label/passing-data.md)). 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:

<div align="left"><figure><img src="https://iceteagroup.com/docs/media/clip0006.png" alt=""><figcaption><p>Field list with Input Items and Report Variables in List &#x26; Label</p></figcaption></figure></div>

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.

{% hint style="info" %}
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.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.iceteagroup.com/general/ported-reports/list-and-label/input-items.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.