# Report Conversion

The main difference between Report Builder and List & Label is the underlying architecture. Report Builder is based on a line-based approach and can only handle one result set for a report. List & Label follows a page-oriented structure and can host a report container on a page which in turn can contain a number of tables, graphs or cross tabs. When a report is converted from Report Builder to List & Label, Ice Porter creates a report container automatically and places a table object inside the report container. Most Report Builder elements are ported to elements inside the table of the report container.

While this is a good mapping between the old and new reporting system, it comes with a number of drawbacks especially in the area of page header, footer, and the report header. Ice Porter has project properties that define how such sections should be handled during conversion. Please consult the Ice Porter manual for further information.

<figure><img src="https://iceteagroup.com/docs/media/clip0003.png" alt=""><figcaption><p>Screenshot of the Report Bulder report designer</p></figcaption></figure>

Despite the different architectural approach and List & Label's advanced feature set are both products similar. The data is usually passed manually just as in Report Builder. Therefore, most items from the legacy reports can be ported to the new platform with similar or identical settings.

<figure><img src="https://iceteagroup.com/docs/media/clip0004.png" alt=""><figcaption><p>Screenshot of the List &#x26; Label report designer, that can be shipped royalty free as part of the target application</p></figcaption></figure>

## Totals

List & Label has so called "sum variables" which are used to replace the running totals from Report Builder.


---

# 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/report-conversion.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.