Define a datasource restriction
Define a datasource restriction
Technologies > User Interface Add-Ins > Parts for Reports > Report with Parsed Restriction
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:
<dataSource id="employeeDs">
<table name="em" role="main"/>
<field name="em_id"/>
<restriction type="parsed">
<clause table="em" name="em_std" op="=" value="TECH"/>
</restriction>
</dataSource>
A restriction may be given type
parsed
, shown above, or
sql
:
<restriction type="sql" sql="NOT(project.status LIKE 'Approved%')"/>
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.
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.
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.