# Access Database from Smart Forms
**App Designer** in ONEWEB provides **built‑in database connectors** that allow Smart Forms to access and manage data securely through configuration rather than direct database coding.
Using Smart Forms, developers can define **data sources**, **schemas**, and **data mappings**, while ONEWEB automatically handles all **CRUD (Create, Read, Update, Delete)** operations at runtime.
***
#### **Concept: Data Access via Smart Forms**
From a **Data & Content Management** perspective, Smart Forms provide a **controlled UI layer** for interacting with database data:
* Users never access the database directly
* Data access is always governed through entities and modules
* Business rules, access logic, and governance remain enforced
This ensures consistent and safe data usage across the application.
***
### Configure Database Access
#### Step 1: Configure Data Source
App Designer allows users to configure database connectivity through the **Datasource Configuration** screen.
In this screen, users can:
* Define the database connection
* Select the target schema
* Manage connection properties centrally
Once configured, the data source becomes available for entity configuration.
***
#### Step 2: Associate Data Source with Entity
After defining the data source, users can assign it at the **Entity Configuration** level.
This step links the entity—and all its Smart Forms—to the selected database schema.
***
### Map Modules and Fields
Once the entity is linked to a data source, users can map UI structures to database structures.
***
#### Step 3: Map Module to Database Table
Each module within an entity represents a logical data group.
To map a module to a table:
1. Click the **Edit** icon to open **Module Configuration**
2. Select the database table to associate with the module
***
#### Step 4: Map Fields to Table Columns
Each Smart Form field must be mapped to a database column to enable data persistence and retrieval.
To map a field:
1. Click the **Edit** icon on the field to open **Field Configuration**
2. Select the associated database column
***
### Enable Search Capabilities
To allow Smart Forms to search database records:
* Enable **SearchCriteria** for fields used as filters
* Enable **ShowSearch** for fields shown in search results
***
#### Trigger Search Action
Add an **Entity Button** with:
* Page Action: `ENTITY_SEARCH`
* Button Action: `searchResult()`
***
### Enable Data Insert and Update
To persist data changes:
* Add **Entity Buttons** with `saveEntity()`
* Available save options:
* `saveEntity()` – save and navigate
* `saveDraftEntity()` – save and stay on page
* `saveEntityCommit()` – save with explicit commit
#### Insert Mode
Use Page Action: `ENTITY_INSERT`
#### Update Mode
Use Page Action: `ENTITY_UPDATE`
***
### Summary
**Smart Forms provide a structured and governed way to access databases through the UX/UI layer**.
With App Designer, developers can:
* Configure data sources and schemas visually
* Map entities, modules, and fields to database structures
* Enable searching, insertion, and updating of data
* Rely on ONEWEB to manage all CRUD operations securely
This model ensures that **database access remains controlled, maintainable, and aligned with Data & Content Management best practices**.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.onewebstack.com/building-apps/data-and-content-management/database-access-management/data-access-from-ux-ui/access-database-from-smart-forms.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
