BaseSettings

### 1. Overview
 The `BaseSettings` table stores core application-level configuration parameters, specifically related to service endpoints (`UrlBase`) and associated credentials (`Password`). This table typically contains a single row of data used by the application backend to resolve local or remote service addresses.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **Id** | Integer | No | Primary unique identifier for the settings record. | e.g., `1` | `WHERE Id = 1` |
 | **UrlBase** | String | Yes | The root URL for internal or external API services. | e.g., `http://localhost:8080/` | `SELECT UrlBase FROM BaseSettings` |
 | **Password** | String | Yes | Credential/Security token used for authentication against the UrlBase. | e.g., `1` | Authentication logic |
 
 *Note: The `index` column appearing in raw data objects is likely a technical row identifier from the data ingestion process and is not defined in the authoritative schema map.*
 
 ### 3. Relationships & Join Map
 
 Based on the provided physical schema map, `BaseSettings` is a **standalone configuration table**. It does not follow the standard `compcode` (Company Code) pattern found in the transactional or master data tables (e.g., `itemmas`, `invhdr`).
 
 * **Potential Join (Likely):**
  * **dbo.pass1**: Linked conceptually via `Password` if the system uses a shared authentication secret across application settings and user profiles, though this is not a standard foreign key relationship.
 * **Usage Pattern:** Usually accessed via a `SELECT TOP 1` query during application initialization to set global environment variables.