Blog: Posts from October, 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(9) OAuth Scopes(1) OAuth2(13) Offline(20) Offline Apps(4) Offline Sync(5) Oracle(11) PKCE(2) Postgre SQL(1) PostgreSQL(2) PWA(2) QR codes(2) Rapid Application Development(5) Reading Pane(2) Release Notes(183) Reports(48) REST(29) RESTful(29) RESTful Workshop(15) RFID tags(1) SaaS(7) Security(81) 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 October, 2012
Friday, October 19, 2012PrintSubscribe
Order Form Sample–Part 9

When creating a new order, the first item that will be entered will probably be the customer. Due to the denormalized nature of Northwind database, the customer information is stored in the table Customers, and the Orders table references a customer via a foreign key field CustomerID. Upon creating a new order, it would be convenient if the user were prompted to either select an existing customer or create a new one. When the customer is selected, the shipping information should be copied from the customer to the order.

Switch back to the Designer. In the Project Explorer, double-click on Order Form / c101 / view1 / grid1 / CustomerID –> CustomerCompanyName / CustomerID (String(5)) field reference node.

CustomerID field reference node under the CustomerID data field of grid1 view.

Enter the following settings for CustomerID:

Property New Value
Data Value Field CustomerID
Data Text Field CompanyName
Copy

ShipName=ContactName
ShipAddress=Address
ShipCity=City
ShipRegion=Region
ShipPostalCode=PostalCode
ShipCountry=Country

Search on Start true
Activate If Blank true
Lookup Window Description Select a customer.

Press OK to save the field.

When the customer has been selected, we’d want the application to prompt the user to select the employee handling the order. To make this part easier, let’s add photos of each employee in the lookup.

In the Project Explorer, double-click on Order Form / c101 / view1 (Orders) / grid1 / EmployeeID –> EmployeeLastName / EmployeeID (Int32) field reference node.

EmployeeID field reference node under the EmployeeID data field of grid1 view.

Change the following settings for EmployeeID:

Property New Value
Activate If Blank true
Lookup window description Select an employee.

Press OK to save the record.

Switch to the Controllers tab at the bottom of the Project Explorer. Expand the Fields and Views nodes of Employees controller. Drag and drop Employees / Fields / Photo (Byte[]) field node onto Employees / Views / grid1 view node.

Dropping the Photo field node onto 'grid1' view node.     A Photo data field has been created in 'grid1' view.

On the Project Designer toolbar, press Browse, and wait for the application to load. Navigate to the Order Form page, and press New Orders on the action bar. You will be prompted to select a customer.

When a new order is created, a lookup will open that will prompt selection of a customer.

When you search for and select a customer, you will then be prompted to select an employee. You can see the photo for each employee as well.

Lookup screen prompting selection of an employee. The photo for each employee is displayed.

Select the employee, and you will see that the shipping fields have been populated from the selected customer.

New Orders form with Customer and Employee selected. Shipping information from the customer has been copied over.

Friday, October 19, 2012PrintSubscribe
Order Form Sample–Part 8

Now that the Order Form page has been set up, we will want to customize several settings. First, we shall optimize the Orders controller. The list of order is currently displayed in alphabetical order of Customer Company Name. It would make more sense to sort the orders according to the date the order was made.

Switch back to the Designer. In the Project Explorer, double-click on Order Form / c101 / view1 (Orders) / grid1 data view node.

View 'grid1' of Orders data controller, accessed view data view 'view1' on the Order Form page.

Change the Sort Expression to the following:

Property New Value
Sort Expression OrderDate desc

Press OK to save the view. On the toolbar, press Browse to regenerate the application. If you navigate to Order Form page, you will see that the orders are sorted in descending order of Order Date.

The list of orders has been sorted in descending order of Order Date.

Friday, October 19, 2012PrintSubscribe
Order Form Sample–Part 7

Let’s create a new page in the application. Switch back to the web application generator, click on the “OrderForm” project name, and press Design.

The design environment allows you to change logical aspects of the project, and consists of two primary elements. The Project Designer, on the left side of the screen, displays a list of objects or properties of the selected object. On the right side of the screen, the Project Explorer allows you to browse and manipulate pages, controllers, and user controls. At the top of the screen, there are several buttons. The Generate button regenerates the web application and displays it in a built-in browser window, called Preview. The Browse button will regenerate the application and open it in your default browser. The Exit button goes back to the web application generator.

The Project Browser and Project Explorer panes of the Project Designer window.

Let’s add a new page called Order Form. In the toolbar of the Project Explorer, press the New Page icon.

New Page context menu option on the toolbar of the Project Explorer.

Give this page the following settings:

Property Value
Name OrderForm
Description This is the order management form.
Style Miscellaneous
About This Page This is the order management form.
Roles (blank)

Press OK to save the page. The page will be added to the bottom of the hierarchy. Drag the new Order Form page node to the right side of Home node to place it second in the hierarchy.

Dropping Order Form page node on the right side of Home page.    Order Form page has been placed second in the hierarchy.

We’ll need to add a container to this page to store the data views. In the Explorer, right-click on the Order Form page, and press New Container.

New Container context menu option on a page node in the Project Explorer.

None of the default properties need to be changed, so just press OK to save the container.

Let’s instantiate two controllers on the page. In the Project Explorer, switch to the Controllers tab. While holding Ctrl key, select Orders and OrderDetails nodes in that order. Right-click and select Copy.

Copy context menu option for Orders and OrderDetails controllers.

Switch back to the Pages tab. Right-click on the container and press Paste. The data controllers will be added to the container as data views.

Paste context menu option on container 'c101' in the Order Form page.     Orders and OrderDetails instantiated as data views on the Order Form.

Drag Order Form / c101 / view2 (OrderDetails) / grid1 / OrderID data field node onto Order Form / c101 / view1 (Orders) data view node. This will configure a master-detail relationship between the two views, with OrderID as the filtered field.

Dropping OrderID data field node onto view1 data view node to establish a master-detail relationship.     Master-detail relationship established between view2 and view1.

Double-click on Order Form / c101 / view2 (OrderDetails) data view node. Change the following settings:

Property New Values
Page Size 300
Show View Description false
Show View Selector false
Show Pager None

Press OK to save the data view. In the Project Explorer, right-click on Order Form page node, and press View in Browser.

View in Browser context menu option for Order Form page node.

Wait for the web application to be generated, and it will open in your default browser. Log in, and you will see Order Form page on the menu bar and the site map.

Order Form page present on the site menu and site map.

Click on the Order Form link, and you will see a list of orders.

A list of orders displayed on the Order Form.

Select an order, and relevant order details will appear underneath.

When an order is selected, order details are displayed underneath.