Table 5490 "Onboarding Signal"
Base Application · System.Feedback
Across versions
- BC23-30present
Base Application · System.Feedback · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Access | Internal |
| Extensible | false |
| DataClassification | OrganizationIdentifiableInformation |
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 | No. | Integer | Used as primary key caption | AutoIncrement |
| 2 | Company Name | Text[30] | — | |
| 3 | Onboarding Completed | Boolean | — | |
| 4 | Onboarding Signal Type | Enum “Onboarding Signal Type” | — | enum Enum 7580 “Onboarding Signal Type” |
| 5 | Onboarding Start Date | Date | — | |
| 6 | Onboarding Complete Date | Date | — | |
| 7 | Extension ID | Guid | — |
Keys
- key1: No.
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: "Onboarding Signal"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.