Designer

Labels
AJAX(112) App Studio(9) 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(178) 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(184) 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(3) 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
Designer
Thursday, November 29, 2012PrintSubscribe
Multi-Field Copy with an SQL Business Rule

It may be necessary for similar values to be copied from a lookup to a record.

When a simple copy operation is required, use the Copy property on the lookup field. For more complex copying operations, a business rule can be implemented. Let’s implement an SQL business rule to copy shipping information from a customer to an order in a sample Northwind web application.

Start the Project Designer. In the Project Explorer, switch to the Controllers tab and double-click on Orders / Fields / ShipName node.

ShipName field in the Orders controller in the Project Explorer.

Change the following properties.

Property Value
The value of the field is calculated by a business rule expression true
Context Fields CustomerID

Press OK to save the field. Right-click on Orders / Business Rules node and press New Business Rule.

New Business Rule context menu option in the Orders controller.

Give this rule the following properties.

Property Value
Type SQL
Command Name New|Calculate
Phase Execute
Script
if @CustomerID is not null
begin
     select 
        @ShipName = ContactName,
        @ShipAddress = Address,
        @ShipCity = City,
        @ShipRegion = Region,
        @ShipPostalCode = PostalCode,
        @ShipCountry = Country
     from Customers 
     where 
         CustomerID = @CustomerID
end

Press OK to save the business rule. On the toolbar, press Browse to generate the web application.

Navigate to the Customers page. Select a customer from the list, and a list of orders will appear underneath. On the action bar, press New Orders. The shipping fields will be prepopulated with the customer shipping information.

New Orders form on the Customers page prepopulated with customer shipping information.

Navigate to the Orders page. On the action bar, press New Orders. The ship fields will be blank.

New Orders form on the Orders page. Customer is not selected, and the shipping fields are blank.

Use the Customer Company Name lookup to select a customer. The ship fields will automatically be populated with the values from the customer.

A customer has been selected. Shipping information has been populated.

Thursday, November 29, 2012PrintSubscribe
Working with Field Outputs in Designer

A field output specifies a link between data controller commands configured to execute after Insert and the identity-based primary key field of the table.

Field outputs can be found on the Field Outputs tab on a command properties page.

Field Outputs tab on the Command page in the Project Browser.

They can also be found on the Field Outputs tab on a field properties page.

Field Outputs tab on the Field page in the Project Browser.

Option New | New Field Output on the action bar will create a new field output.

New Field Output action bar action in the Project Browser.

The details of a field output can be seen by clicking on the field name or using the context menu option Open.

Open context menu action in the Field Outputs tab in the Project Browser.

Field outputs can be deleted using the context menu option Delete.

Delete context menu option for a field output in the Project Browser.

Field outputs do not have a node in the Project Explorer.

Tuesday, November 27, 2012PrintSubscribe
Advanced User Manager for Custom Membership and Role Provider: Adding “Roles” Tab

Let’s add a “Roles” tab on the Users page to allow management of roles. When a role is selected, users corresponding to the role will be displayed below. In order to create this “implied” master-detail relationship, a “UsersInRole” view must be created that will use a custom command to extract the RoleID.

Creating “Users In Role” View

Right-click on Users / Views / grid1 view node, and press Copy.

Copying 'grid1' view of Users controller.

Right-click on Users / Views node, and press Paste. A duplicate of the view will be created.

Pasting a view onto Users controller.     A duplicate of 'grid1' called 'v100' has been created.

Double-click on Users / Views / v100 node. Next to the Command property, select the New Command icon.

Creating a new command.

Assign these values.

Property Value
Id command2
Text
select
    "Users"."UserID" "UserID"
    ,"Users"."UserName" "UserName"
    ,"Users"."Password" "Password"
    ,"Users"."Email" "Email"
    ,"Users"."Comment" "Comment"
    ,"Users"."PasswordQuestion" "PasswordQuestion"
    ,"Users"."PasswordAnswer" "PasswordAnswer"
    ,"Users"."IsApproved" "IsApproved"
    ,"Users"."LastActivityDate" "LastActivityDate"
    ,"Users"."LastLoginDate" "LastLoginDate"
    ,"Users"."LastPasswordChangedDate" "LastPasswordChangedDate"
    ,"Users"."CreationDate" "CreationDate"
    ,"Users"."IsLockedOut" "IsLockedOut"
    ,"Users"."LastLockedOutDate" "LastLockedOutDate"
    ,"Users"."FailedPasswordAttemptCount" "FailedPasswordAttemptCount"
    ,"Users"."FailedPasswordAttemptWindowStart" 
        "FailedPasswordAttemptWindowStart"
    ,"Users"."FailedPasswordAnswerAttemptCount" 
        "FailedPasswordAnswerAttemptCount"
    ,"Users"."FailedPasswordAnswerAttemptWindowStart" 
        "FailedPasswordAnswerAttemptWindowStart"
    ,UserRoles.RoleID RoleID
from "dbo"."Users" "Users"
left join UserRoles on Users.UserID = UserRoles.UserID
Type Text
Event Select

Press OK to create the command and insert it into the property. Also make the following changes:

Property Value
Label Users In Role
Show In View Selector false

Press OK to save. In the Project Explorer, right-click on Users / Views / v100 and press Rename.

Renaming the view 'v100' using the context menu option.

Change the name to “UsersInRole” and press Enter on your keyboard to save.

View ID has been changed to 'UsersInRole'.

Adding “RoleID” Field

Right-click on Users / Fields node, and press New Field.

New Field context menu option for Users controller.

Assign the following properties:

Property Value
Name RoleID
Type Int32
The field is hidden from users. true
Label Role ID
Allow Query-by-Example true

Press OK to save the field. Drop Users / Fields / RoleID field node onto Users / Views / UsersInRole to create a data field and append it to the view.

Dropping RoleID field onto view 'UsersInRole'.     'RoleID' data field created in view 'UsersInRole'.

Adding Roles Tab to Users Page

Switch to the Controllers tab in the Project Explorer. While holding Ctrl key, click on Roles and Users controller nodes in that order. Right-click and press Copy.

Copying the Roles and Users controllers.

Switch back to the Pages tab. Right-click on Users / container1 node, and press Paste. The controllers will be instantiated as views in the container.

Pasting onto 'container1' of Users page.      The copied controllers have been instantiated as views in the container.

Double-click on Users / container1 / view1 (Users) data view node.

Selecting 'view1' on the Users page.

Change the following properties.

Property New Value
Activator Tab
Text Users
Search By First Letter true

Press OK to save. Double-click on Users / container1 / view2 (Roles) node.

Selecting 'view2' on the Users page.

Make the following changes.

Property New Value
Activator Tab
Text Roles

Save the data view. Double-click on Users / container1 / view3 (Users) node.

Selecting 'view3' on the Users page.

Make these changes:

Property New Value
View UsersInRole
Activator Tab
Text Roles

Save the data view. Expand Users / container1 / view3 (Users, UsersInRole) / UsersInRole node. Drop RoleID data field node onto Users / container1 / view2 (Roles) to establish a master-detail relationship.

Dropping 'RoleID' data field of UsersInRole view onto 'view2' in Users page.      A master-detail relationship has been created between 'view3' and 'view2'.