Learn to configure the
<table> element for Pull Reports™ Ad Hoc
report and data service software.
Catalog Configuration Java API analog:
<table> element represents one relational database table within the report configuration. Every
has exactly one
child called the base table which is always included in Export Report REST API
SQL joins and export results. Nest additional
<table>s within child
<relationship> elements of the base table
to extend the report's join tree.
<table> must map to one TABLE (or VIEW or MATERIALIZED VIEW) in the underlying relational database
name attribute or contain a child
<subquery> element which
Global tables: A global
configured as a direct child of a
<catalog>. Global tables allow
<table> configuration to be used multiple times within a
<table>s are referenced
<table_ref>s. For an example of global table usage see
the section called “Catalog with multiple
id of the
table resource path statements.
<table_ref>s nested within
with the same
<table> join parent must have unique
id values between themselves.
This requirement ensures that each table resource path
uniquely identifies one
<table_ref> within a
The human readable table name.
The name of the table or view in the database. This name
may be dot
(.) preceded with a schema name. For instance,
name attribute is required unless the
<table> has a child
<subquery> element. The
attribute is also required if the
<table> has a child a
<subquery> with a
provider attribute and the referenced SubqueryProvider
returns a Subquery which in turn returns the empty Optional from the
A comma separated list of
ids which are the table's primary keys.
for example usage.