Blog: Posts from August, 2012

Labels
AJAX(112) App Studio(7) Apple(1) Application Builder(245) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) Barcode(2) Barcodes(3) BLOB(18) Business Rules(1) Business Rules/Logic(140) BYOD(13) Caching(2) Calendar(5) Charts(29) Cloud(14) Cloud On Time(2) Cloud On Time for Windows 7(2) Code Generator(54) Collaboration(11) command line(1) Conflict Detection(1) Content Management System(12) COT Tools for Excel(26) CRUD(1) Custom Actions(1) Data Aquarium Framework(122) Data Sheet(9) Data Sources(22) Database Lookups(50) Deployment(22) Designer(177) Device(1) DotNetNuke(12) EASE(20) Email(6) Features(101) Firebird(1) Form Builder(14) Globalization and Localization(6) How To(1) Hypermedia(2) Inline Editing(1) Installation(5) JavaScript(20) Kiosk(1) Low Code(3) Mac(1) Many-To-Many(4) Maps(6) Master/Detail(36) Microservices(4) Mobile(63) Mode Builder(3) Model Builder(3) MySQL(10) Native Apps(5) News(18) OAuth(8) OAuth Scopes(1) OAuth2(11) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(10) PKCE(2) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(180) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(80) SharePoint(12) SPA(6) SQL Anywhere(3) SQL Server(26) SSO(1) Stored Procedure(4) Teamwork(15) Tips and Tricks(87) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(338) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(40) Web.Config(9) Workflow(28)
Archive
Blog
Posts from August, 2012
Monday, August 13, 2012PrintSubscribe
Working with Fields

A field represents a column of a data row. There are physical and virtual fields. Virtual fields are not derived from a physical column of a data table – their values are computed at runtime. Bindings of fields to views are called data fields.

In the Project Explorer, fields are contained under the Fields node of a controller. If an asterisk (*) is present after the name of the field, the field is required. The field type and length are displayed in parentheses. Some fields fields may display “read-only” label.

Fields under the Fields node of a controller in the Project Explorer.

Creating a Field

A field can be created by using the New Field context menu option on the Fields node.

New Field context menu option in the Project Explorer.

Moving Fields

Fields can be moved using drag and drop operations.

Dropping a field node onto another field node will place the field after the target field.

CategoryID field dropped on CategoryName field in the Project Explorer.     CategoryID field moved after CategoryName in the Project Explorer.

Dropping a field node on the right side of another field node will place it after the target field.

CategoryName dropped on the right side of CategoryID field.     CategoryName field moved after CategoryID field in the Project Explorer.

Dropping a field node on the left side of another field node will place it before the target field.

Picture field dropped on the left side of Description field.     Picture field node placed after Description in the Project Explorer.

Fields can be copied to a different controller by dragging onto the controller or Fields node. The original field will not be deleted.

Description field dropped on CategorySalesfor1997 controller node.     Description field placed at the bottom of Fields node of CategorySalesfor1997 controller in the Project Explorer.

Creating Data Fields

When fields are dropped onto a view or category, they will be instantiated as data fields in the target view. When the field is dropped onto a form view, the data fields will be appended to the last category.

Dropping two fields onto a view node.     Two data fields created in view1.

Cloning a Field

A field can be copied by dropping onto the controller or Fields node while holding Ctrl key. The name of the clone will be appended with a number, and the new field will be configured as a calculated field that reflects the physical column in the database. Use context menu option Copy on the field and use Paste on the controller or Fields node to create a clone.

Description field dropped on Categories controller node while holding Ctrl key on the keyboard.     Description field duplicated as 'Description_1' in the Categories controller.

Create Standard Validator and Converter

Validation and conversion business rules can be quickly created using the Add Validator and Add Converter context menu options. Code, SQL, and JavaScript options are available.

Add SQL Validator context menu option for a field in the Project Explorer.

When an option is selected, the field is configured as calculated, and a business rule will be created.

Validator for CategoryName field automatically created in the Project Explorer.

Deleting a Field

Fields can be deleted using the context menu option Delete. This will also remove all data fields, items, and field outputs.

Delete context menu option in the Project Explorer.

Monday, August 13, 2012PrintSubscribe
Working with Fields in Designer

Fields represent properties of business objects. These properties are reflecting physical columns of a data row or a computed value based on other columns.

A complete list of data controller fields can be seen by switching to the All Fields tab on the Home page of the Project Browser.

All Fields tab on the Home page of the Project Browser displays all fields in the web application

The Fields tab on a controller page will display all fields of that specific controller.

Fields tab on a controller page displays the fields of a controller.

Clicking on the name of a field or the Open context menu option will display the details of the field.

Open context menu option in the Project Browser.     Field detail form in the Project Browser.

The Sync context menu option will select the relevant node in the Project Explorer.

Sync context menu option in the Project Browser.     CategoryName field node synchronized in the Project Explorer.

If the field is configured as a static item lookup, the items are specified under the Items tab on the Fields page.

List of static field items on the Items tab of the Fields page.

Binding of fields to data controller views are called data fields. They can be accessed via the Data Fields tab.

Data fields for a field are accessible via the Data Fields tab on the Field page.

Fields can be dragged to the views to create a binding (data field). When dropped on a form view, the data fields will be appended to the last category of the view. When dropped on any other type of view, the data field is created under the view node itself.

Dropping two fields onto a view node.     Two data fields created in view1.

Fields names can be changed using the Rename context menu option in the Project Explorer. The Rename operation will also update all references to the field, including the alias in the command text.

Rename context menu option in the Project Explorer.     CategoryName field in Rename mode in the Project Explorer.

Fields can be deleted using the Project Explorer context menu option Delete.

Delete context menu option in the Project Explorer.

Fields can be quickly found by their property values using Navigate To window.

LastName field found in Navigate To using the search terms 'lastname employees'.

Monday, August 13, 2012PrintSubscribe
Overview of Fields

When an application is generated from a database, field definitions are created to match the columns of a table. Additional fields can be automatically added to controllers by configuring a denormalization field map. Virtual fields can represent computed data.

Field Properties:

Property Description
Activate If Blank Specifies that the lookup will be activated when the value is blank.
Allow Last Entered Values Specifies that the most recently entered value by the user will be the default value for the next record. Simplifies mass entry of records with values that are not expected to change frequently.
Allow Null Values Specifies that the field can blank.
Allow Query-by-Example Enables advanced filtering options for the field in grid views.
Allow Sorting Enables sorting for the field in grid views.
Code Default Specifies the default value that will be applied when the new record form is opened.
Code Formula Specifies a formula written in the programming language of the project that will return a field value.
Code Value Specifies a value that will be calculated every time the record is updated.
Context Fields Specifies which fields, when changed, will cause calculated fields to be refreshed.
Controller Specifies the controller the field belongs to.
Copy Specifies a list of fields that will be copied from the selected lookup item.
Data Format String Specifies the data format string for the value. Available strings are: Standard Numeric, Standard Date/Time, Custom Date/Time, HTML.
Data Text Field Specifies the field that will be displayed to the end user.
Data Value Field Specifies the field value that will be saved.
Defines the primary key. Specifies if the field is the primary key. The client library uses the primary key to select, update, and delete data.
Dynamic Configuration Specifies fields that can provide dynamic values for the field properties.
Edit Mask Specifies an edit mask that will validate the entered field value.
Editor Specifies the name of a custom editor.
Format On Client When disabled, specifies that the server will format the field using the supplied data format string.
HTML Encoding Specifies that the field value will be displayed in full. When disabled, HTML in the field will be rendered.
Items Data Controller Specifies the controller that will be used to look up data.
Items Data View Specifies the view of the controller that will be used to look up data.
Items Style Specifies the style that will be used to display items.
Label Specifies the label that will be displayed in the user interface.
Length Specifies the length of the field.
Lookup Window Description Specifies a description on the lookup window.
Mask Type Specifies the type of edit mask to be used.
Name Specifies the name of the field. If the field matches a physical column, the name of the field should match the name assigned in the command.
New Data View Specifies the view that will be used when the New Record icon is selected. If blank, the icon will not be displayed.
On Demand Handler Specifies a name for an automatically created handler that will retrieve the blob field.
On Demand Style Specifies the method used to display the blob field. Available options are thumbnail and link.
Page Size Specifies the number of items displayed in the lookup view.
Read Roles Specifies which roles are permitted to view the field.
Search by First Letter When enabled, displays quick first letter filters at the top of the lookup view.
Search on Start Specifies that the lookup view will have advanced search bar open by default.
Server Default Specifies the default value that will be applied when the record is saved.
Show In Summary Specifies that the field will be displayed in the summary when a record is selected.
Source Fields Specifies primary key fields that uniquely identify the source record.
SQL Formula Specifies a formula computed on the server that will return the field value.
The value of the field is calculated by a business rule expression. Specifies that the the field value is produced by a business rule method. Context fields must be specified to cause the calculation.
The value of this field is computed at run-time by SQL expression. Specifies that the field is not physically present in the table.
The field is included in all data views but remains hidden from users. Specifies that the field is hidden in the user interface.
Type Specifies the data type of the field.
Value is retrieved on demand Specifies that the field requires special handling.
Values of this field cannot be edited Specifies that the field is read-only.
Write Roles Specifies which roles are permitted to edit the field.

Learn how to work with fields in the Project Designer.

Learn to drag and drop categories in the Project Explorer.

Common Tasks:

Task Description
Read-Only Data Access Learn how to restrict access to fields by roles.
Implicit Filters with Dynamic Access Control Rules Learn how to filter lookup items based on values in the record.
Creating a New Many-to-Many Field Learn how to configure a many-to-many field.
Multiple Value Field Learn how to configure a static multiple value field.