Properties of fields: User interface texts
Contents
On the User interface texts tab, which is present when you have selected a new or existing data dictionary field in a database, you may specify label texts for screen fields, menu texts for methods that are associated with this field and/or label texts to indicate relations (if this is a linked field) for the Related records view in Axiell Collections. In most existing applications, these texts are specified in the Screen editor on entry field level, in the Label properties, and respectively in the application setup on method level, in the Menu texts. To prevent redundancy in new applications or when adding fields to existing applications, you could enter the user interface texts on data dictionary field level, to have to specify these texts only once.
Click here for information on how to edit properties in general. On the current tab you'll find the following settings:
In Axiell Collections, screen texts for fields will only be used to represent fields (instead of their actual field names) in the column headers of the Result set view.
Method texts are not supported in Axiell Collections.
This setting is meant for partially setting up the current field (if it is a linked field) for the optional Related records view in Axiell Collections. This view can provide an alternate overview of all linked records in one or more single-sided linked fields in the current record, while in the linked data source it can provide an overview of all records in the primary database linking to the current record: the latter records are grouped (and thus repeated) per data source from which they are accessible, so that the user may choose the data source in which to open a related record. For reversely linked records, this view provides an overview of all linked records in one or more linked fields in the current record, on both sides of the reverse link. Consider applying this functionality only to a limited list of linked fields, or it will become difficult for the user to select the relation(s) he or she would like to see in the view. This functionality solves the problem where some reversely linked fields slow down performance because of hundreds or thousands of occurrences in such a linked field. Since the Related records view is much faster in retrieving that many links, you could consider converting such reversely linked fields into single-sided linked fields that never have that many occurrences: this does require some data conversion/clean-up though.
For this Relation texts option, it doesn't matter if the currently edited linked field is a single-sided or a reversely linked field. Just provide the label to indicate the forward relation in as many languages as required by your user base. A forward relation label should indicate that it lists links from the currently displayed record to records in another data source. For the creator field in database Collect for example, you could specify an English forward relation label such as This record > Persons and institutions or This record > creators or just Creator(s).The text in this example will be visible in objects data sources.
To complete the setup for this field, also fill in the Relation format string property on the Relation fields tab. And for single-sided linked fields, also specify Reverse relation texts below and a Format string for the feedback database (if present) in the linked database. For reverse linked fields, do also specify appropriate Relation texts and a Relation format string in the reversely linked field in the linked database.
Note: you cannot use the {0} system variable for these forward relation texts.
See the full topic for more information about how to set up the Related records view.
This setting is meant for partially setting up the current field (if it is a linked field) for the optional Related records view in Axiell Collections. This view can provide an alternate overview of all linked records in one or more single-sided linked fields in the current record, while in the linked data source it can provide an overview of all records in the primary database linking to the current record: the latter records are grouped (and thus repeated) per data source from which they are accessible, so that the user may choose the data source in which to open a related record. For reversely linked records, this view provides an overview of all linked records in one or more linked fields in the current record, on both sides of the reverse link. Consider applying this functionality only to a limited list of linked fields, or it will become difficult for the user to select the relation(s) he or she would like to see in the view. This functionality solves the problem where some reversely linked fields slow down performance because of hundreds or thousands of occurrences in such a linked field. Since the Related records view is much faster in retrieving that many links, you could consider converting such reversely linked fields into single-sided linked fields that never have that many occurrences: this does require some data conversion/clean-up though.
For this Reverse relation texts option, the currently edited field should be a single-sided linked field, not a reversely linked field. For a single-sided linked field, just provide the label to indicate the reverse relation that will be visible in the linked data source, in as many languages as required by your user base. A reverse relation label should indicate that it lists links from a specific field in another data source to the currently displayed record. For the creator field in database Collect for example, you could specify an English reverse relation label such as Objects > this record or Objects (creators) > this record or Links from Creator {0} to this record. The text in this example will be visible in records in the Persons and institutions data source.
Optionally you can use the {0} system variable to have Axiell Collections insert the target data source name in between brackets. Collections will list a found record underneath as many data sources as it is accessible in, so if e.g. an object record is accessible from both the Objects data source as well as from the Internal object catalogue, Collections will list this record for both data sources. So applying {0} is very useful for distinguishing the two lists: it allows the user to select the data source to jump to (the context in which the target record will be opened), because he or she may have different access rights in different data sources. And if you don't use {0}, the user will have no clue as to why some lists of related records are displayed twice either. So a reverse relation text like Objects {0} (creators) > this record, could become visible as the two list headers Objects (Full object catalogue) (creators) > this record and Objects (Internal object catalogue) (creators) > this record for example, depending on the actual target data source names.
(The system variable {0} can only be used for Reverse relation texts, not for Relation texts.)
To complete the setup for this field, also fill in the Relation format string property on the Relation fields tab. And for single-sided linked fields, also specify Relation texts above and a Format string for the feedback database (if present) in the linked database.
See the full topic for more information about how to set up the Related records view.