Table 1543 "Flow Service Configuration"
Base Application · System.Automation
Across versions
- BC23present
- BC24declaration changed
- BC25unchanged
- BC261 fields changed
- BC27-30unchanged
Neighbourhood 1 connected objects and pages
Base Application · System.Automation · captioned “Power Automate Service Configuration” · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Power Automate Service Configuration |
| DataClassification | CustomerContent |
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 | Primary Key Δ BC26 | Code[10] | — | |
| 2 | Flow Service | Option | Specifies the Power Automate service configuration: Production Service, Testing Service (TIP 1), or Testing Service (TIP 2). via Page 6415 “Flow Service Configuration” | OptionCaption: Production Service,Testing Service (TIP 1),Testing Service (TIP 2) |
Keys
- Key1: Primary Key (clustered)
Pages and codeunits on this table
- Page 6415 “Flow Service Configuration” (source table)
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: "Flow Service Configuration"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.