Table 5395 "Dataverse Entity Change"
Base Application · Microsoft.Integration.Dataverse
Across versions
- BC23present
- BC24declaration changed
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · Microsoft.Integration.Dataverse · BC23-30 · source at ea08af5e · facts from BC29
Properties
| Property | Value |
|---|---|
| Caption | Dataverse Entity Change |
| 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 | Entry No. | Integer | — | AutoIncrement; DataClassification SystemMetadata |
| 2 | Entity Name | Text[248] | — | DataClassification SystemMetadata |
Keys
- Key1: Entry No. (clustered)
Triggers
OnInsert
Pages and codeunits on this table
- Page 5395 “Dataverse Entity Changes API” (source table)
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 5330 “CRM Integration Management” (1 call:
OnInsert → ReactivateJobForTable)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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: "Dataverse Entity Change"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.