Anveo Page Elements

Anveo Page Elements define the depiction of an Anveo Page in the Anveo Web Portal. An Anveo Page Element has the following properties:

Table No.

The field Table No. corresponds to a number of a Dynamics table.

Element Type

The Element Type defines whether the Anveo Page Element deals with the layout of a card or a list and for which clients the Anveo Page is designed.

For the Anveo Web Portal only Anveo Pages of  Element Type Web Portal – Card or Web Portal – List will be available.


The marker Visible can be used to temporarily hide an Anveo Page Element, for instance when the element has not been conclusively installed yet at the time of publication.


With the Readonly marker you can indicate whether the Anveo Page Element is supposed to be protected against changes. 

If this write protection is enabled on an Anveo Page Element, no changes can be carried out on the fields displayed.  

Whether the Anveo User is able to save the data on his device depends on the access rights which have been set up for the Anveo Page and the table.

Default Mode on Open Page

Defines what mode the Anveo Page will be in when opened. You can select inbetween View and Edit.

A Read-only write protection on the field level means that this field cannot be modified, independent of whether the page has been unblocked afterward by implementing a function.

Additional Properties of Anveo Page Elements

If you select an Anveo Page Element on the setup card of an Anveo Page and click on Additional Properties, you receive the following configuration options:

Double Click Action/Direct Link

On the tab Double Click Action/Direct Link you can specify if you want to open another Anveo Page or perform an action on double clicking.

Open Anveo Page

If you want to open an Anveo Page, type in the field
Open Anveo Page the code of the Anveo Page you want to open.

The entered Anveo Page needs for the corresponding client at least one Anveo Page Element. Otherwise the Anveo Page can not be found and therefore not opened in the client.

The double click is only possible on lists in the Anveo Web Portal with activated write protection. In Anveo Web Portal an arrow at the right edge of the current line indicates the possibility for a direct link. 

Custom TableRelation

Normally the relationship between the current Anveo Page and the one to be opened is created automatically via the global setup in the Anveo Page Table-Field Relation of the Anveo Client Suite. If a deviating relationship exists between the two or a relationship that cannot be depicted via simple field relations, a code can be indicated in the Custom TableRelation field that specifies this relation defined in C/AL code or via Anveo Script (see here).

Action Code

If you want to execute some other desired action via double click, enter the code for the action that you have programmed via C/AL code or Anveo Script into the field Action Code.

Behavior Tab

In the Behavior Tab you can define the behavior of the Anveo Page to specific events, as well as preferences for the appearance.

Write Behavior

In the field Write Behavior can be used to establish how the data is going to be transferred from the Anveo Page from Anveo Web Portal into Dynamics. The following options are available to choose from:


Each change in any desired field is validated and saved in Dynamics directly upon leaving the field. One advantage of this setting is that all data gets into the system immediately and is thus visible and usable for all other users of the database at an early stage.

The Direct setting can only be used when the primary key for a table is defined and set, so it is already available in SQL server database. For example, this setting does not function in the Sales Price table because the primary key consists of a total of eight fields.


Delayed  write behavior is the opposite of direct write behavior. When creating a new record, the record is first filed in a temporary table in Dynamics and e.g. marked in red on the user interface. This temporarily filed record is not handed over to the destination table in Dynamics and stored in the database until the user presses Save, modifies another record or closes the Anveo Page. If an existing record is modified, that record can be first marked in orange by the client for the time being. As with newly created records, the record will equally not be saved in Dynamics until the user carries out another action such as explicitly clicking on Save, closing the Anveo Page, editing a different record or creating another new record.

As with all other forms of write behavior, with this type the inputs equally run through the Validate-trigger for the corresponding table. Invisible fields on the user interface and parameter values filled by these kinds of triggers are saved as well.

One advantage of this setting is that, unlike Direct write behavior, only one write or insert operation is performed in the destination table. One disadvantage is that all users access a temporary table. In the event of a large number of accesses this could lead to a so-called “bottleneck” and reduce clients performance.

It makes sense to use the 
Delayed setting when the primary key of the underlying table consists of more than one field and the table has more than one undefined value.


Defined and Primary key write behavior are mixed forms of the write behaviors 
Direct and Delayed. Using Defined  write behavior, the point in time at which the data itself is written can be defined via C/AL code. For instance, a record can be kept temporary until such time when a condition is fulfilled and the release approval to write is thus granted. One code example for this is located in the codeunit 
ACF Events Sales & Marketing, function IsWriteBack.

Primary Key

Primary Key write behavior represents a special form of Defined write behavior. This write behavior corresponds to Direct write behavior when fields are modified which are not part of the primary key. In cases where all fields that are part of the primary key are modified, this write behavior corresponds to Defined write behavior. The record is saved in Dynamics precisely at the point when the first field in the record is validated which is not part of the primary key. This means that all fields which are part of the primary key have to be filled out first before all the other fields can be modified.

Custom Table Relation Subelement

In the field Custom Table Relation Subelement you can enter the code belonging to an individualized table relation for a Anveo Page Element that is subordinate to the first element (see TODO Section 6.1.). This “customized” table relation is one which you yourself have defined, for example in the codeunit ACF Events, function CustomWebPageRelation.

Paging Counter per Page

In the field Paging Counter per Page you can specify the maximum number of records that are supposed to be depicted on one Anveo Page Element type list. At a value of 0 the setting is adopted by the setup. It is fundamentally recommended to set this value so that only the exact number of records are displayed that the Anveo Page height in the client allows. This increases both the loading speed and the display speed in the Anveo Web Portal. The Anveo Web Portal shows all records, because all records are saved locally on the device. 

Scroll hoizontally

In the field Scroll hoizontally you can determine whether a list should be horizontally scrollable to depict for example lists in table layout with many fields.

Edit Mode Next Field

In the field Edit Mode Next Field you can define the direction in which direction the cursor should jump after the tab key is pressed to speed up inputs. You can use this setting only in editable lists in Anveo Web Portal.


You can use the property AutoSplitKey as same property from Dynamics to insert data.

Sorting Tab

In the Sorting Tab you can choose a key of a table and set the sorting on an Anveo Page.


Here you can select the Key of the table how the data on the Anveo Page will be sorted.


Here you can select the sort order. Possible options are ascending and descending.

Mobile Tab

The Mobile Tab contains properties, that are needed in the Anveo Mobile App.

Short Press Tab

In the Short Press Tab you can define the behavior of an Anveo Page in Anveo Mobile App when a list entry is pressed shortly.

Long Press Tab

In the Long Press Tab you can define the behavior of an Anveo Page in the Anveo Mobile App when a list entry is pressed long.