The TABLE report type creates a column table based on the data inputted. The following data structures are available:
All TABLE report types will be string processed being converted to html. This means that variables and parameters can be put in the data, and will be parsed out in runtime. For example $param1$ will be replaced with the value represented by param1.
XML does not require an identifier because its start is unique. The query can just be the XML document. The report will generate the HTML for the XML to become a table. Example query:
<?xml version="1.0"?>
<catalog>
<book id="bk101">
<author>Gambardella, Matthew</author>
<title>XML Developer's Guide</title>
<genre>Computer</genre>
<price>44.95</price>
<publish_date>2000-10-01</publish_date>
<description>An in-depth look at creating applications
with XML.</description>
</book>
<book id="bk102">
<author>Ralls, Kim</author>
<title>Midnight Rain</title>
<genre>Fantasy</genre>
<price>5.95</price>
<publish_date>2000-12-16</publish_date>
<description>A former architect battles corporate zombies,
an evil sorceress, and her own childhood to become queen
of the world.</description>
</book>
</catalog>
An SQL function is automatically formatted in a table arrangement, so the report will convert that table into an html table. An example report:
SELECT
a.email,
a.select_role,
concat("{report:udeclms_delete_user:", b.`Uuid`, "}") as "Remove Employee"
FROM sys_user AS b
LEFT JOIN bloom_form_udeclms_add_user AS a
ON a.email = b.`user`
WHERE a.select_role is NOT NULL AND a.email is NOT NULL