Table 20351 "Conn. App Country/Region"
ConnectivityApps
Across versions
- BC23-28not present
- BC29-30present
ConnectivityApps · BC29-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Extensible | false |
| TableType | Temporary |
| DataClassification | SystemMetadata |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | App Id | Guid | — | |
| 2 | Country/Region | Enum “Conn. Apps Country/Region” | — | enum Enum 20351 “Conn. Apps Country/Region” |
| 3 | Category | Enum “Connectivity Apps Category” | — | enum Enum 20350 “Connectivity Apps Category” |
| 4 | Localization | Enum “Connectivity Apps Localization” | — | enum Enum 20352 “Connectivity Apps Localization” |
Keys
- Key1: App Id, Country/Region, Localization (clustered)
- Key2: Country/Region, Category, Localization
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Conn. App Country/Region"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.