# One‑to‑One (1-1) Module
The **One‑to‑One (1–1) Module** is used to display and manage **a single record** in the database.\
It is primarily designed for **form‑based data entry and editing**, where each Entity instance corresponds to exactly one database record.
The 1–1 Module uses a **row and column layout**, allowing users to design Smart Forms flexibly according to UI and business requirements.
***
### Purpose of 1–1 Module
The One‑to‑One (1–1) Module is suitable for:
* Capturing or editing **one record at a time**
* Representing **main or header data** of an Entity
* Designing input‑driven Smart Forms
* Managing master data with structured layouts
#### Typical Use Cases
* Customer profile
* Order header
* Employee information
* Master data maintenance screens
***
### Layout Characteristics
Key layout characteristics of a 1–1 Module include:
* **Row and Column based layout**
* Supports **1, 2, or 3 column layouts**
* Fields are placed using **drag and drop**
* Optimized for **form‑style interaction**, not tabular data
To create a 1–1 Module, simply **drag the 1–1 Module icon** into the desired Tab and start designing the layout.
***
### 1–1 Module Configuration Overview
The 1–1 Module provides a configuration panel that contains several property groups (1–5), as shown below:
***
### Open Module Configuration
 - This icon opens the **Module Configuration** window, where database mapping, key generation, and module behavior are defined.
***
### One‑to‑One Module Configuration Properties
| Module Item | Mandatory | Description |
| -------------- | --------- | ----------------------------------------- |
| Module ID | Yes | System‑generated unique identifier |
| Module Name | Yes | User‑defined name for the module |
| Table Name | Yes | Database table mapped to this module |
| Template Code | Yes | UI template (inherits from Entity) |
| Theme Code | Yes | UI theme (inherits from Entity) |
| Module Key | Yes | Primary key field of the table |
| Prefix | No | Prefix added to auto‑generated keys |
| Postfix | No | Suffix added to auto‑generated keys |
| KeyLen | Yes | Length of the primary key |
| Sequence | Yes | Database sequence used for key generation |
| SQL Select Row | No | Custom SQL to retrieve a single record |
| SQL Work Queue | No | Custom SQL for search page integration |
| View Mode Flag | No | Opens module in read‑only mode |
| Paging Flag | No | Enables paging when used in search |
| Ordering Flag | No | Enables sorting when applicable |
> **Note**\
> Properties such as `SQL Select Row` are specific to **1–1 Modules** and are used to retrieve a **single record**.
***
### Layout and Design Tools for 1–1 Module
#### Drag Module into Layout
 - Used to place the module into rows and columns in a **Multi‑Column Tab Form** layout.
***
#### Configure Column Layout
Defines how many columns the module uses:
* 1 Column
* 2 Columns
* 3 Columns
Click **Accept** to apply the selected layout.
***
#### Add Rows and Columns
* First icon → Add **Column**
* Second icon → Add **Row**
Users can add multiple rows and columns to design complex form layouts.
***
#### Delete Module
 - This icon removes the 1–1 Module from the Smart Form layout.\
(Does **not** delete the database table.)
***
### Usage Guidelines
* Use **1–1 Module** for single‑record data only
* Ideal for core or master entity information
* Avoid using for repeating or line‑item data
* Always map to **one database table**
* Use custom SQL only when default behavior is insufficient
* Save frequently while designing layouts
***
### Summary
The **One‑to‑One (1–1) Module** is the primary building block for **form‑based Smart Forms** in ONEWEB.
Key points:
* Manages **single database records**
* Uses **row and column layout**
* Ideal for master or header data
* Highly flexible form design
* Strong integration with database and entity configuration
Using the 1–1 Module correctly ensures Smart Forms are **clean, intuitive, and aligned with business data structures**.
---
# 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/oneweb-platform-th/designer-reference/app-designer/entity/create-new-entity/module/one-to-one-1-1-module.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.
