The JDBC views are simply an administrator’s advanced search filter that has been saved and exposed to an API user.
As seen below is an example saved advanced search in the Employee model where the list is filtered by a single ‘Company’.
Important Items
The ability to create saved filters that can be exposed to JDBC requires all of the following conditions to be met.
Admin must have role access to Security > Api User Manager
The API User must have API Role Access to the view module
The exposed view must be active
The exposed view must have a valid schema setup in APIHub
Creating a new JDBC View
Login Into Admin
Open the desired module
Apply a filter ← IMPORTANT - be sure to click Apply before you attempt to save
Click Save
You will be presented with this popup
Filter Name - Filter name which is visible in admin advanced search
Override If Exists - When checked, and the filter/view already exists, it will override the existing filter and view with your changes.
Expose To Api - Will make the View visible from JDBC
Api View Name - View name which will display in JDBC
Api Roles - Limits which API roles will be able to see the view from JDBC
Active - Active flag
5. Click Save
Now the View will be visible from the JDBC explorer as long as all the previous conditions were met.
