Skip to main content
Define a datasource restriction
- Last updated
-
-
Save as PDF
<div id="mc-main-content" role="main">
<h1>
Define a datasource restriction
</h1>
<p>
<span class="glosstext">
Technologies > User Interface Add-Ins > Parts for Reports > Report with Parsed Restriction
</span>
</p>
<p>
Restrictions work as filters, allowing the user to see only records
that make sense in each specific situation. Restrictions can be defined
directly in the AXVW, as shown below:
</p>
<p>
</p>
<p class="CodeBox">
<dataSource id="employeeDs">
<br />
<table name="em" role="main"/>
<br />
<field name="em_id"/>
<b>
<br />
<restriction type="parsed">
<br />
<clause table="em" name="em_std" op="=" value="TECH"/>
<br />
</restriction>
</b>
<br />
</dataSource>
<code style="font-family: monospace;">
</code>
</p>
<p>
A restriction may be given type
<code class="codeColor">
parsed
</code>
, shown above, or
<code class="codeColor">
sql
</code>
:
</p>
<p class="CodeBox">
<restriction type="sql" sql="NOT(project.status LIKE 'Approved%')"/>
</p>
<p>
Restrictions may also be applied dynamically from one view to another.
For example, the user might set the search criteria in the console window,
and click on the Search button – the console window will apply selected
values as a restriction to the target report view.
</p>
<p>
Additional restrictions can also be assigned to specific users, and
applied to any view that the user navigates to. These restrictions are called
VPA (Virtual Private Archibus) restrictions and are defined by the Database
Manager.
</p>
<p>
Restrictions can filter out all available records, in which case the
form view will display empty values, and the report view will display
no records.
<br />
</p>
<p class="Note">
View:
<a href="http://localhost:8080/archibus/schema/ab-products/solutions/parts/grid/ab-ex-report-grid-rm-restriction.axvw" target="_blank">
http://localhost:8080/archibus/schema/ab-products/solutions/parts/grid/ab-ex-report-grid-rm-restriction.axvw
</a>
</p>
</div>
