Extended view
The extended view shows an object as Business Central runs it: the base object with the fields, controls, actions and other items its extensions add inlined where they land. It has the features of the Object view, and an extension icon marks each inlined item.
Opening it
- Select the Extended Object tab at the bottom of the Objects page. It is the tab an object opens on.
- Select View › Extended Object.
- Press Ctrl+1.

| # | Name | Description |
|---|---|---|
| 1 | Inlined item | The field the extension adds, shown in the base page where it lands: before its anchor. |
| 2 | Anchor | The base page's control the extension adds the field before. |
| 3 | Extension icon | Marks an item that an extension adds. Hover over it for the extension; select it to go to the item's declaration in the extension object. |
The extension's side
The extension object itself shows each change with its kind and its anchor. Here the page extension adds a field
before VATReturnStatus, the field inlined above.

| # | Name | Description |
|---|---|---|
| 1 | Change | The kind of change: Add Controls Before is addbefore, which adds controls before the anchor. |
| 2 | Anchor | The base control the change is anchored on. Select it to go to the control in the base page. |
| 3 | Controls to add | The controls the change adds before the anchor. |
Changed properties and table relations
A property an extension sets replaces the base object's value, as it does at runtime. The extended view shows both: the replaced value struck through, then the value in effect. Where several extensions set the same property, every replaced value is struck through and only the last one applied is in effect.
A TableRelation works the other way: an extension's table relation adds to the field's, typically
a relation for a new enum value. The extended view lists the base relation and every added one under the field,
none struck through.
Moved controls and actions
A control or action that a page extension moves shows where it ends up, with an arrow before its name for the kind of move:
| Arrow | Move | In the extension |
|---|---|---|
| ↑ | Before the anchor | movebefore |
| ↓ | After the anchor | moveafter |
| ⇑ | First in the group | movefirst |
| ⇓ | Last in the group | movelast |
Point at the arrow to see the move, such as “Moved Before by extension”, and the path of the extension that makes it. Select the arrow to go to the move in the extension.

| # | Name | Description |
|---|---|---|
| 1 | Move arrow | The kind of move; select it to go to the move in the extension. |
| 2 | Tooltip | The move and the path of the extension that makes it. |
Inherited procedures
An interface that extends other interfaces gains their procedures. Its extended view lists them after its own, one group per interface, headed Inherited from and the interface's name, with its namespace below when it has one.
A codeunit that implements an interface whose procedures carry a default implementation runs that body for every procedure it does not declare itself. Its extended view lists those procedures the same way, under the interface that declares them.
Both groups show while Show inherited interface procedures is on, on the Settings page.

| # | Name | Description |
|---|---|---|
| 1 | Inherited from | The interface that declares the procedures below. Select its name to open it, or the namespace under it to show that namespace on the Namespaces page. |
| 2 | Inherited procedure | A procedure the object gets from that interface. |
Order of changes
When several extensions change the same place, such as two extensions that add controls before the same control, the result depends on the order the changes are applied. Prism applies them in the topological order of the module dependencies, as the Business Central runtime does.