Selecting fields


Query fields could be added by "Select Fields..." button.


Navigation tree is build upon entity relation information and is started from "Query.Data Source" entity as a base level.


By default (if you have not enabled object list fields in relations) navigation tree represents left join logic, that means selecting any paths in tree will lead in getting path direction goes from many to one (according to database foreign key).

But you also can create right joins by altering entity relation properties.


You can alter position of fields using Up Down buttons on top of the grid.


Change path option


Change path option could be useful when field looses its path (path is shown in Path column of grid with fields).


Field looses its path when:

  • entity field that used in path was deleted
  • you changed Data Source of the Query and new data source doesn't have field with the same name or path


Of course you can just delete broken fields, but that could lead to broken Screens, Wizards or other objects that used this field.


(!) You can check where you current field is used on Dependencies tab.


So if you have any dependencies for your field it is safer to set a new path than recreate (delete than add) a field.


Other scenario when Change Path option could be useful is making changes to data representation if you have a lot of Screens using one Query.


(!) If you delete a field any dependency (a link from other objects to your field) would be also deleted. Even if you add a field with the same name dependency would not come back.


Field order could be altered by up/down buttons:


Query Field properties


Section

Name

Description

in list

Path

Path to field build upon entity relation information. Could be changed by Change Path button.

Basic

Name

Machine name of a field. Should be machine friendly.

Basic

Display Name

Display Name is automatically set from corresponding entity field. If display name not changed in query field then any changes in entity field display name would automatically transfer to query field.

Basic

Format

Display format for a field. See Formats chapter fr details.

This option doesn't change query data but used in screen blocks as a default value for format.

Basic

Sorting

Sort data by this field. Could be ascending, descending or disabled.

Basic

Sorting Order

Sorting order when data sorted by several fields.

Basic

Type

Type is inherited from entity field type and cannot be changed.

User Interface

Description

Useful to make notes about purpose of this Query Field.

Security

Read

Select a permission or built in option for security logic.


Built in options:

<private> means that this option available only on server side.

<auto> means permission would be auto created. You should run permission creation script on deployment to be able to see updated permissions. See Deployment chapter.

<parent> means that current query Security.Read setting would be used.

<inherited> means that entity field Security.Read setting would be used.


If field is restricted by permissions then data would be replaced by null, 0 or empty string depending on type.

Security

Update

Select a permission or built in option for security logic.


Built in options:

<private> means that this option available only on server side.

<auto> means permission would be auto created. You should run permission creation script on deployment to be able to see updated permissions. See Deployment chapter.

<parent> means that current query Security.Update setting would be used.

<inherited> means that entity field Security.Update setting would be used.


If field is restricted by permissions then data would be replaced by null, 0 or empty string depending on type.


There is a special type of query field - Computed field.

Created with the Personal Edition of HelpNDoc: Easy EPub and documentation editor