You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If checked, this field will be displayed in the detail view but not editable.
52
+
This is useful in many scenarios, including forcing a default value (or automatic value), calculated fields, fields that are populated using custom code or a third party app, .. etc.
If you check this option, the current field will be the primary key of the current table.
57
+
In AppGini, Every table must have a single primary key field in order to uniquely identify records of the table (multi-field primary keys are not supported by AppGini).
Check this property to left-pad numeric data types with zeros when they are displayed, so that the total number of digits matches the field's 'Length' property.
62
+
For example, if the field length is 5 and is set as zero-fill, a field value of 22 would be displayed as 00022.
63
+
64
+
### Required
65
+
If you check this property, users must provide a value for this field before submitting the form.
66
+
If a user attempts to submit a record while leaving a required field empty, they'd see an error message similar to the one below.
67
+
If you set the field as read-only, auto-increment or hidden in detail view, this property will be ignored.
If checked, this field will be displayed as a rich area in the detail view. A rich area provides advanced formatting features not available in a normal text area. For example, you can change the font/font size, colors, add links, add photos, ... etc.
While defining the properties for the ID field (likely named "id"), look for an option labeled "Auto Increment". This option appear as a checkbox with an "Auto Increment" selection.
77
+
78
+
### Unique
79
+
The data values in this field cannot be repeated if you check this property. This is similar to the Primary key property except that unique fields can be empty (null).
80
+
If a user tries to enter a value that already exists into a unique field, they'll see an error message like the one below.
If checked, this field will be displayed as a text area in the detail view. This is useful if you want to allow multiple lines in a field, for example to enter addresses or notes.
If checked, the current field is not displayed in the table view. This may be useful if you want to hide some fields or to decrease the width of tables.
Specifies the width in pixels of the column that will display data from this field in the table view.
129
+
Please note that the width specified is the minimum (rather than exact) width. If the total width of all columns in the table view is less than the page width, each column would expand based on the ratio of its specified width to the total table width.
130
+
131
+
132
+
### Media, Lookup field, Options list...etc
133
+
The various options in these tabs specify the behavior and appearance of the current field.
Configures this field as a link to the detail view (the default behavior), a link to a URL, an email link, or no link. Click the 'Configure' button to change the link behavior.
Image Configures this field to accept an image upload and display as a full-size image or a thumbnail.
144
+
145
+
his works only if the field has a textual data type (Char, Varchar, Text, ..etc). This is because the field actually stores the image file name, while the image itself is uploaded to the storage of the server running your AppGini app.
Configures this field as a file upload field. This works only if the field has a textual data type (Char, Varchar, Text, ..etc).
151
+
This is because the field actually stores the file name, while the file itself is uploaded to the storage of the server running your AppGini app.
152
+
In the configuration window, you can specify the maximum file size in KB that users are allowed to upload. Also, you can specify whether you want to delete the file from the server if the record is deleted. You can also configure how the field is displayed to users.
If you want to set this field as a lookup field (foreign key), select its parent table from this menu. A parent table is the table which has the field containing the source data for the lookup field.
168
+
For more information about lookup fields, refer to the section 'Understanding lookup fields' in the online help.
The advanced window allows you to specify a custom SQL query for populating the lookup drop-down.
174
+
You can use this typically to filter the possible values for this lookup field. For example, you can display products that are not discontinued rather than all products by adding a WHERE condition in the SQL query.
175
+
176
+
### Lookup field > Parent caption field 1
177
+
If this is a lookup field (foreign key), select the field to be used as the first part of the caption from this menu. A parent caption is the caption or alias that appears to the user in the lookup drop-down.
178
+
For more information about lookup fields, refer to the section 'Understanding lookup fields' in the online help.
If this is a lookup field (foreign key), select the field to be used as the second part of the caption from this menu. A parent caption is the caption or alias that appears to the user in the lookup drop-down.
192
+
For more information about lookup fields, refer to the section 'Understanding lookup fields' in the online help.
When this option is checked, the lookup field is displayed as a set of radio buttons rather than a drop down menu. This applies only if the lookup field is not set as 'Auto-fill'.
Check this option to limit the contents of the lookup drop down to only the parent records that the logged member is allowed to view. If not checked, all parent records are listed regardless of the member's permissions.
### Field properties > Link to parent record in detail view
207
+
In the detail view, lookup fields can have an adjacent link to the parent record. This drop down specifies whether to show that link, and how the link behaves when clicked.
If you want to limit the possible values for a field to a specific list of values, type the allowable values here, separated by double semi-colons.
213
+
The first screenshot below shows an example of how to specify the list values. The second screenshot below it shows how the field will be displayed to users (options are sorted alphabetically in the drop-down).
Choose a popular predefined set of options from the quick list instead of having to type them manually.
219
+
To add your own predefined list, create a text file containing the list and save it into the 'add-ons' folder inside your AppGini installation folder. The extension of your list file must be '.Ist'.
If you choose to display an options list as a drop-down list, users can select a value from the drop-down, and can search for values by typing part of their content in the search box.
225
+
Recommended if you have a large number of options.
If you choose to display an options list as a multiple-choice list box, users can select one or more values from the drop-down, and can search for values by typing part of their content in the search box.
231
+
To use this option, the field data type must be a TEXT or BLOB type.
232
+
The screenshot below shows an example where the user has selected 2 values form the drop-down.
If this field is an options list, and you choose to display it as radio buttons, the values of the list are displayed as radio button options, each on a separate line. The advantage of radio buttons is that they are very easy to use and the user can see all the possible options without scrolling.
238
+
Not recommended though if you have a large number of options, as this will cause the form to become too long. Use a drop-down list in this case.
239
+
Options are sorted in the same order you enter them if you choose radio buttons.
240
+
To hide the 'None' option, set the field as required.
Use this option if you want to apply a special format to the data stored in this field.
246
+
Examples of special formats include currency formats, Date/time formats, ... etc.
247
+
You can add or edit data formats by editing the file 'C:\Program Files\AppGini\add-ons\dataFormats.cfg' in a text editor.
248
+
Rules: Each data format on a separate line. The line begins with the description of the data format, followed by a semi-colon (;) and a space, followed by the format code (written in MySQL syntax). The description of the data format can't include semi-colons.
### Calculated field > Automatically calculate the value of this field using the following SQL query
253
+
This is an advanced feature that requires some SQL knowledge.
254
+
Instead of receiving user input, or a default value, calculated fields are populated by running the specified SQL query, and storing the returned value.
255
+
The SQL query should return a single value: single row and single column. Use the 'Query helper' button to open an advanced query editor that makes it much easier to build queries. The list of variables at the right allows you to insert special placeholders in the SQL query, to be replaced by their
256
+
corresponding values before running the query. For more details and examples, please refer to the online help.
257
+
258
+
### Show technical documentation page in the admin area
259
+
Technical documentation is a way of adding comments/documentation to your app. If the option 'Show technical documentation page in the admin area' is checked, the documentation will also be visible to the admin user rather than just in AppGini. Documentation text can optionally include HTML code. Bootstrap CSS classes can also be used.
0 commit comments