* COMING SOON *
The AutoCompleteTextBox can be used as an alternative to the Combobox and the LookupPicker controls. You start typing letters and the control will filter and display only those values that match the letters.
An example of an AutoCompleteTextBox control follows:
The value of the control is in the following format (when accessed from script using the GetValue() method) :
// Bound to static values
NAME1
// Bound to lookup entity
ID1;#NAME1
Type : AutoCompleteTextBox
Provides a unique name for the control.
Indicates if the control is
Sets if the control will be enabled or disabled when the forms handles a new record
Sets if the control will be enabled or disabled when the forms handles an existing record
Marks the cotnrol as Required.
By default, the system recognizes required fields and marks them with this flag. Additionaly, controls can be marked as required event if the bound column is not.
Set an expression then will be evaluated during run-time and enable or disable the control.
The expression must be in javascript and should return a boolean value.
Dependencies between controls are automatically identified and the expression is re-calculated every time a control affecting the formula changes.
Example :
form.GetControl("c_Status").GetValue() != "Open" && form.UserInGroup("Administrators")
Define a valid formula (using javascript) that will be evaluated during runtime to show or hide the control.
The expression should return a boolean value.
For example :
form.FieldValue("c_Status") != "Rejected" || form.UserID() == "1"
This property defines how the control will get its value.
Here are the available options :
A static text must be set in the appropriate designer control.
A javascript expression must be set that will provide the value for the control.
If the formula contains references to other controls, dependencies will be automatically identifies during run-time and the value will be updated to reflect changes.
Example :
form.FieldValue("c_Active") ? "Yes" : "No"
There is an additional option that instructs the form to perform calculations only for new records. Existing records will keep their original value.
A predefined list query is bound to the value of the control. So during form initialization, the specified list query is executed and if it returns any item, it selects the first one and it will apply the value to the label based on the following rule :
If a Field Name has been selected in the corresponding box, that specific column will be used from the list item to fill the control value.
If the Field Name is left blank, the first column retrieved will be used.
The same as above, the required web service is selected and after the web service retrieves data, the first item will be used to update the control value. If no Field Name is set, the control will receive the first field of the retrieved item.
Works the same way ListQueries and Web Service works.
The default value has any effect only of the control is bound to a list column.
For unbound controls, the default value is ignored.
You may set a static value here or use a formula by starting your input with the "equals" (=) sign.
Example :
1;#CategoryA
Defines the width of the control.
When the value is zero, the maximum allowed width will be used.
Defines the control height.
If the value is zero, the height property will not be set.
Defines the horizontal alignment of the parent cell (values : left, right, center)
Defines the vertical alignment of the parent cell (values : top, bottom, center)
Defines the fore color of the control
Defines the Background color of the control.
Defines the color of the parent cell.
Declares the font size of the text
Sets the margin applied to the control, that is, the spacing between the control and the cell borders.
Changes the weight of the font used
Changes the font style for the control text
This control belongs in the Lookup controls and can provide users with a set of values to select from.
The values can be retrieved from a variety of methods :
This is the default method if the underlying column is a lookup column.
You must define the url of the site containing the target list
Select the required list from the dropdown control.
Selecting a view is optional.
If a view is selected then a) the criteria of the view will be combined with the criteria provided here, b) the sorting of the view will be used.
You can provide multiple search criteria by opening the criteria editor.
Select the field that will be used as the display member of the result set
Select the field that will be used as the value member of the result set.
You can select a column of the current record that will be used to filter values from the target list
If you selected a value for the "Constraint By" property, you must select the column of the target list that will be filtered by the value of the "Constraint By" column.
The form will automatically identify changes in the control bound to the "Constraint by" column and refresh the lookup data.
If the "Constraint By" and "Match To" properties are filled, then the "Query Type" property should be set to set the type of query that will be performed. (Values: Text, Lookup)
You may select a List Query already defined in the "List Queries" section of the designer.
All the query parameters (columns retrieved, criteria, sorting, etc) should be defined in the List Query definition.
In the Lookup Details section, users should select the required list query and the Display and Value field of the control. Both fields should be retrieved by the list query.
Lookup values from web services can be used as lookup values for controls.
The web service should be already defined in the "Web Services" section of the designer.
The Display and Value fields should be set here by selecting 2 of the fields retrieved by the web service.
Static values can be defined as lookup values for a lookup control.
If the underlying column is a choice column, then the list of values cannot be changed by the user.
This option should only be used for SharePoint 2007.
If a control is bound to column that references BDC data then the options here should be already filled in.
You can define the Application instance, the BDC Entity and Display/Value fields.
This option should only be used in SharePoint 2010.
SharePoint 2010 supports the definition of data sets across multiple sites and site collections using a hierarchical structure. You can define the TermSet (id or name), the Anchor ID (optional : the guid of the term that will be used as the root term for search) and the "Taxonomy Keyword" checkbox which defines if search will be performed across term sets.
Set this property to TRUE to allow the user to fill their own value. Use this for fill-in choice or textual columns.
Note: Setting this property to TRUE will make the control save only the display field value if it is setup as a lookup field.
Set this property to "True" to force the control to send only the Value Member value of the underlying lookup value when saving its value.
Normally lookup controls that load data from other lists, use the ID;#TITLE format to save data
Defines if the results will be sorted by the Display Field
If the internal name of a column is supplied, the retrieved results will be filtered allowing unique values for that specific field
Values : Id, Title
Applies formatting for the value field when the value is a lookup value (ID;#TITLE format).
If "Id" is used, then the "ID" part of the value will be used for the value member of the control.
If "Title" is used then the "Name" part of the value will be used.
Values : Id, Title
Applies formatting for the display field when the value is a lookup value (ID;#TITLE format)
If "Id" is used, then the "ID" part of the value will be used for the display member of the control.
If "Title" is used then the "Name" part of the value will be used.
You can use the "ValueFieldFormat" and "DisplayFieldFormat" properties of this control to fill a lookup controls with all the available values found in a lookup column of a list.
For example :
To fill an AutoCompleteTextBox with all the customers that have placed an order within the last month (Customer is a lookup column inside the Orders list) :
Select the "Orders" list as the target list applying the appropriate date criteria.
The "Display Field" should be set to "Customer"
The "Value Field" should be set to "Customer"
Example value of the Customer column inside the Orders list : "32;#CUSTOMER-A"
The ValueFieldFormat should be set to "Id" (getting the "32" part)
The DisplayFieldFormat should be set to "Title" (getting the "CUSTOMER-A" part)
The combined value has the required format for the lookup control (ID;#NAME)
Unique customers can be enforced using the "UniqueField" property of the control.
Sets the script that will be executed at the value-change event of the control.
Example :
var value = form.GetControl("c_Title").GetValue();
if (value == "Open") form.HideSection("Details");
else form.ShowSection("Details");