Page 5395 "Dataverse Entity Changes API"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23-30present
Neighbourhood 1 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Extensible | false |
| SourceTable | Dataverse Entity Change |
| PageType | API |
Fields on this page
Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).
| Group | Control | Shows | ToolTip |
|---|---|---|---|
| Group | Id | Rec.SystemId |
— |
| Entity Name | Entity Name | — |
Relations
- source table Table 5395 “Dataverse Entity Change”
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: "page", object_name: "Dataverse Entity Changes API"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.