Blog: Posts from February, 2013

AJAX(112) Apple(1) Application Builder(242) Application Factory(207) ASP.NET(95) ASP.NET 3.5(45) ASP.NET Code Generator(72) ASP.NET Membership(28) Azure(18) 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(11) 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) DotNetNuke(12) EASE(20) Email(6) Features(99) Firebird(1) Form Builder(14) Globalization and Localization(6) Hypermedia(2) Installation(4) 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(15) OAuth(5) OAuth Scopes(1) OAuth2(6) Offline(14) Oracle(10) PKCE(1) PostgreSQL(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(163) Reports(48) REST(26) RESTful(21) RESTful Workshop(13) RFID tags(1) SaaS(7) Security(75) SharePoint(12) SPA(5) SQL Anywhere(3) SQL Server(26) Stored Procedure(4) Teamwork(15) Tips and Tricks(81) Tools for Excel(2) Touch UI(93) Transactions(5) Tutorials(183) Universal Windows Platform(3) User Interface(331) Video Tutorial(37) Web 2.0(100) Web App Generator(101) Web Application Generator(607) Web Form Builder(39) Web.Config(9) Workflow(28)
Posts from February, 2013
Thursday, February 28, 2013PrintSubscribe
“Freezing” Data Fields

A common practice in data sheets is to “freeze” a column so that essential information is always displayed for each row. The second generation data sheet allows both freezing columns at run-time, as well as configuring a column to be frozen at design-time.

Freezing at Run-Time

Create a sample Northwind web application. Browse the site, and navigate to the Order Details page. On the action bar, press Actions | Show in Data Sheet.

Changing the grid view to data sheet view.

Activate the column header dropdown for Product Name, and press Freeze.

Activating 'Freeze' option for Product Name column.

All columns up to the frozen column will change color. When the data sheet is scrolled to the right, the frozen columns will continue to be displayed.

Frozen columns 'Order Customer#' and 'Product Name' continue to be displayed when the data sheet is scrolled to the right.

Columns can be added or removed from the freeze by activating the Freeze option for that column. You may unfreeze the column by activating the column header dropdown and pressing Unfreeze.

Unfreezing the Product Name column.

Freezing at Design-Time

Start the Project Designer. In the Project Explorer, double-click on Customers / Order Details / container1 / view1 (OrderDetails, grid1) / grid1 / ProductID –> ProductProductName data field node.

Data field 'ProductID' of view 'grid1'.

Assign a tag.

Property New Value
Tags data-sheet-freeze

Press OK to save the field. On the toolbar, press Browse. On the action bar, press Actions | Show in Data Sheet.

Changing the grid view to data sheet view.

When the data sheet loads, the Product Name column will be frozen by default.

The column 'Product Name' is frozen by default.

The frozen columns can still be changed by the user using the method described in the previous section.

Wednesday, February 27, 2013PrintSubscribe
Configuring Hierarchy

The “hierarchy-parent” tag can be used to present a hierarchical view of information.

Note that hierarchy is only available in the second generation data sheet view.

First, create the HR sample web application using Oracle Database Engine.

Adding a New Page

When generation is complete, activate the Project Designer. On the Project Explorer toolbar, click on the New Page icon.

Creating a new page.

Assign a name to the page:

Property Value
Name Hierarchy

Press OK to save. Drop the new Hierarchy page node on the right side of Home page to place it second in the menu.

Dropping Hierarchy page onto Home page.     Hierarchy page is second in the menu.

Switch to the Controllers tab. Right-click on EMPLOYEES data controller and press Copy.

Copying EMPLOYEES controller.

Switch back to the Pages tab. Right-click on Hierarchy page and press Paste. The data controller will be instantiated as a data view.

Pasting onto Hierarchy page.     The data view has been instantiated as a data view in a container on the page.

Configuring Hierarchy in Data Sheet

Double-click on Hierarchy / c101 / view1 (EMPLOYEES) / grid1 view node.

View 'grid1' of EMPLOYEES controller.

Change the view type.

Property New Value
Type Data Sheet

Press OK to save. Double-click on Hierarchy / c101 / view1 (EMPLOYEES) / grid1 / MANAGER_ID –> MANAGER_LAST_NAME data field node.

Data field 'MANAGER_ID' of view 'grid1'.

Tag the data field as the hierarchy parent.

Property New Value
Tags hierarchy-parent

Press OK to save.

Viewing the Results

On the toolbar, press Browse. The data sheet will now be organized according to the hierarchy.

Hierarchy in the Oracle sample database.

Wednesday, February 27, 2013PrintSubscribe
Enabling Second Generation Data Sheet Preview

Starting with release, web applications created with Premium or Unlimited edition include a preview of the second generation data sheet view. The new implementation supports horizontal and vertical scrolling, column resizing, and freezing. In addition, applications based on Microsoft SQL Server or Oracle also support hierarchical presentation of data.

The preview does not yet support all capabilities available in the original data sheet. The missing features will be released as soon as they become production-ready. Therefore, the second generation data sheet is disabled by default. If you would like to take it for a spin, make sure to regenerate your web app and follow the instructions below.

Start the web application generator. Create a sample Northwind web app. When generation is complete, click on the project name in the start page of the generator. Then, click Develop to open the project in Visual Studio.

In the Solution Explorer, right-click on ~\App_Code folder, and press Add | Add New Item…


Select Class from the list, and assign a name. Press Add to create the file.


Replace the existing code base with the following:


namespace MyCompany.Data
    public partial class ControllerUtilities
        public override bool SupportsScrollingInDataSheet
            get { return true; }

Visual Basic:

Namespace MyCompany.Data
    Partial Public Class ControllerUtilities
        Public Overrides ReadOnly Property SupportsScrollingInDataSheet As Boolean
                Return True
            End Get
        End Property
    End Class
End Namespace

Save the file and run the web app. Navigate to the Customers page. On the action bar, press Action | Show in Data Sheet.


The grid view will render the second generation data sheet.


The second generation data sheet will be enabled by default when the feature set of the previous implementation is replicated.

To use the original data sheet view implementation, make sure that the SupportsScrollingInDataSheet property of class ControllerUtilities returns false.

Continue to EASE Geo Tagging