Object view

The object view shows the current object: a heading, links to its declaration groups, and three tabs at the bottom. Prism shows the declarations and code, Dependencies what uses the object and what it uses, and Source the object's text. Use it to read an object and to navigate from it.

Opening it

• It is the middle part of the Objects page.
• Select an object in the Object index, in search results or on the Solution page, and it shows that object.

1 2 3 4 5 6

Object context menu

Right-click the object heading, or an object in the Object index, for the object's context menu.

Declaration groups

Under the heading, a link per top-level group of the object, such as fields, keys or triggers, with the number of declarations in it. Select one to scroll the Prism tab to that group. The links are hidden on the Dependencies tab.

Prism tab

1 2 3 4

The Prism tab shows the object's declarations, properties and code. Select a reference to an object, a field or another declaration to navigate to it. Select the name of a declaration, such as a procedure or trigger, to find its usages. Hover over a property name to see where it sits in the object.

Right-click the name of a declaration for:

Find Usages

Lists every place that uses the declaration, as selecting its name does. See Find Usages. Without a license it works for variables and parameters; on other declarations it reads Find Usages (Not enabled in this edition).

Copy Prism Path to Clipboard

Copies the declaration's Prism path. Offered on declarations that have one, such as fields and procedures.

Properties are shown by kind:

Parse error panel

When an object could not be parsed, a Parse error panel takes the place of its declarations on the Prism tab: “Source could not be fully parsed; outline and analysis are unavailable for this object.” Use it to find what to fix in the object's text.

1 2 3 4

When Prism cannot place the error in the source, the panel says “The parser could not place this error in the source” and shows no line, column or source lines. The Object Errors window and the Parse errors list of the Solution page show the summary on one line. See Troubleshooting for what to do about objects that fail to parse.

Context menus on calls in code

Some calls in the code on the Prism tab have a context menu with one item. The mouse pointer changes over a call that has one. Right-click the call for:

1 2

Show inter-table field mappings

On a TRANSFERFIELDS call. Opens the Field Transfer Mappings window window with the record's table as the target and the table of the argument as the source. Offered when both tables are in the store, parse without errors and are different tables.

Go to Key Declaration

On a SETCURRENTKEY call. Goes to the key the call sets, in the record's table. Offered when Prism finds the key.

Go to Trigger Declaration

On an INSERT, MODIFY, MODIFYALL, DELETE, DELETEALL or RENAME call on a record. Goes to the matching trigger of the record's table: OnInsert, OnModify, OnDelete or OnRename. Offered when Prism finds the trigger.

Selecting and copying code

Select a code line to mark it, then select another line to mark the lines between them. Select a marked line's marker to clear it. Prism keeps your marked lines while Remember code line selections is on, on the Settings page.

Right-click a marked line for:

When the clipboard is not available, a copy command says Error trying to copy source code lines to clipboard.; when the text file cannot be written or opened, Open Code with Default Text Editor says Error trying to copy source code lines to text file. Try again.

Right-click the Code header of a trigger or procedure to copy the whole block:

Copy code to new window

Opens all the block's lines in a Code fragment window.

Copy code to clipboard

Copies all the block's lines with their context.

Send a piece of code to a colleague

Use this to send a colleague a piece of code they can find again.

1. On the Prism tab, select the first line, then the last line of the code.
2. Right-click a marked line and choose Copy Code to Clipboard.
3. Paste into the email or ticket.

The text names the store, the object and the declaration above the code. To add notes first, choose Copy Code to New Window instead; see Code fragment window.

Find the same line in the development environment

1. On the Prism tab, select the line.
2. Right-click it and choose Copy Code to Clipboard without Context.
3. In the C/AL editor of the development environment, search for the copied text.

MenuSuite layers

1 2 3 4

MenuSuites are layered: a MenuSuite can add nodes, and change, move or delete the nodes of the MenuSuites below it. The Prism tab sorts each menu node of a MenuSuite by what it does:

The nodes are grouped as Added menu nodes, Modified menu nodes, Re-linked menu nodes and Removed menu nodes, each with a count. Re-linked and removed nodes start collapsed. A MenuSuite with only one kind, such as a base layer, shows a single Menu nodes group.

A node that changes another fits on one line: the change, the node's name, then the MenuSuite that defines the node and what changes, for example next → Customers, Visible = No. Prism finds node names in the nearest MenuSuite at or below the current one in the same family: the navigation pane (ids below 1000) or the departments (1000 and up). Hover over a node to see its GUID; a GUID Prism cannot resolve is shown shortened.

Source tab

The Source tab shows the object's text, read only. It opens on the code the Prism tab was showing, so you do not have to scroll to find your place.

Code colors

Names in code are colored by what they are. Prism resolves each name to its declaration, so a field, a parameter, a procedure and a variable each have a color of their own, also when they belong to another object. Global variables and comments are set in italics, and a variable, parameter or return value that holds a temporary record has a dotted underline. Two calls stand out in colors of their own, since they change what is in the database for good: a record's DELETE and DELETEALL are red, and COMMIT is magenta. A record's other built-in functions, such as INSERT and MODIFY, keep the color of every built-in function.

1 2 3 4 5 6 7

An option value after ::, such as Status::Open, and an object named after an object type, such as PAGE::"Customer Card", have colors of their own. Keywords, text, numbers, operators and brackets are colored by kind. A name Prism cannot resolve has the color of plain text, and selecting it does nothing.

Fields and tables in property values take the same colors: the table and fields of a TableRelation or CalcFormula, with their conditions and filters, the fields of link properties such as SubPageLink, of the filters of view properties such as SourceTableView, and of field lists such as CalcFields.

Hover over a name in code or in a property value for its tooltip: the path from the object down to the declaration, each step with its kind and name, and for a field, variable or parameter its type. For a name Prism cannot resolve, the last step reads Unresolved.

The colors follow the dark or light theme and cannot be changed. The Code fragment window and the preview of Universal Search show code in the same colors; the Source tab does not color it.

Font and line spacing

These settings under Code on the Settings page change how code looks:

Related

• Dependencies tab
• Outline
• Code fragment window
• Find Usages