Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Additional Tools • Supported Browser Platforms • Control Types • Layout Basics • Control Properties • SQL/HANA Tool • SMTP OAuth setup with Microsoft Exchange Online • Using APP Report Maintenance and Delivery • Scheduled Run • Versago & Bizweaver Templates
versago3:from_settings

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
versago3:from_settings [2023/05/01 11:35]
dlee [Content] 		versago3:from_settings [2024/08/28 11:51] (current)
dlee [Lookup List]
Line 45: Line 45:
     * Only one field can be designated with this option.     * Only one field can be designated with this option.
  
- * **Character Length** defines the maximum number of characters that can be entered in a field of the control.+  * **Character Length** defines the maximum number of characters that can be entered in a field of the control.
     * For text fields the value can be less than the number of characters defined in the database if you wish to restrict the value entered.     * For text fields the value can be less than the number of characters defined in the database if you wish to restrict the value entered.
     * For numeric fields the value should be the maximum number of digits you want to accept in the field. Because of the way data is stored this may be greater than the number of bytes defined for the column in the database.     * For numeric fields the value should be the maximum number of digits you want to accept in the field. Because of the way data is stored this may be greater than the number of bytes defined for the column in the database.
Line 63: Line 63:
     * {UserProfile**.**$FirstName} – returns the user’s first name     * {UserProfile**.**$FirstName} – returns the user’s first name
     * {UserProfile**.**$LastName} – returns the user’s last name     * {UserProfile**.**$LastName} – returns the user’s last name
-    * {UserProfile**.**$CopmpanyName} – returns the user’s Company name+    * {UserProfile**.**$CompanyName} – returns the user’s Company name
     * $GETDATE() - returns current date     * $GETDATE() - returns current date
  
Line 73: Line 73:
   * **Formula** is used to provide various types of calculation operations that can be used to populate a field based on values in other fields.   * **Formula** is used to provide various types of calculation operations that can be used to populate a field based on values in other fields.
     * Formulas can only be applied to numeric and date values.     * Formulas can only be applied to numeric and date values.
-    * See [[versago:form_configuration#formulas|Formulas]] for information on the creation and use of formulas.+    * **Calculation** formulas are used to place the results of a computation using values of two (or more) other controls. Fixed values can also be used in control-level calculations. 
 +    * **Aggregate** formulas are used to provide either a sum or average of values in the details (rows) section of the form and report them in a header-level field.  
 + 
 +<WRAP center round info 80%> 
 +Aggregation can only be applied to one field. A formula like SUM(X*Y) will not work. 
 +</WRAP>
  
 ==== Adornment==== ==== Adornment====
Line 148: Line 153:
   - On the “Control Settings” tab, select “Textbox” as the Control Type.   - On the “Control Settings” tab, select “Textbox” as the Control Type.
   - Select the data view to be used from the Lookup Report menu   - Select the data view to be used from the Lookup Report menu
-  - The [ **…**] ellipsis button to the right of the Lookup  menu is used to define Input Fields (i.e. form controls (values) that can be used as input filters to the lookup report) and OutPut Fields (i.e. form controls that will receive their input value from fields in the user-selected record in the lookup report).+  - The [ **…**] ellipsis button to the right of the Lookup  menu is used to define Filters (i.e. form controls values that can be used as input filters to the lookup report) and Mappings (i.e. form controls that will receive their input value from fields in the user-selected record in the lookup report).
     - At least one Output field must be configured. This will be the control where the lookup is being applied and should be the value to be displayed to the user.     - At least one Output field must be configured. This will be the control where the lookup is being applied and should be the value to be displayed to the user.
-    - Additional output fields may also be defined. These are typically other values associated with the lookup value. See the simple example that follows. +    - Additional output fields may also be defined. These are typically other values associated with the lookup value. 
-   +  - The list of values in the lookup will be sorted according to the sorting configured in the look up data view. 
- +
-In this example, we use a lookup to present a list of U.S. states. We want the user to select the state by name, but we want to capture both the name and the associated code. +
- +
-{{  ::versago3:formv2image86.png?384x161  }} +
- +
-In this example the value “Name” is placed in the Column (control) named “Lookup1” and the associated code is placed in the Column (control) named “Lookup2.”+
  
-Note that the controls that receive values do not need to be visible on the form. In this example the “Lookup2” is not displayed to the user even though the value is captured. 
  
  
versago3/from_settings.1682955307.txt.gz · Last modified: 2023/05/01 11:35 by dlee

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki