Data Forms

Data Forms

Brick River Content, Contacts can be edited using any web browser when a Data Form has been created for this purpose.

When a data form is saved, Brick River assigns it's Form Id and creates sample @BRT.DataLink() Helpers that can be pasted to Pages or Layouts - creating links launch the forms.

Important Notes about Data Forms:

  1. Only Administrators can create Data Forms.
  2. Each Data Form is linked to View and that View determines which fields will be included on the form.

    Views which include <Relationship> elements with the attributes: Dependent="true"  or ShowAsTable="true" may not be linked to Data Forms.  These relationship fields will prevent the forms from opening in a browser and display and error page to the user.  Many Views contain this type of <Relationship> element.  Review additional details and directions for removing  or customizing these elements below.
  3. Data Forms may use templates designed for Brick River Registration forms.  If no template is named the Data Form will use the built in System Default Branded Template.
  4. It is almost always the case that updating contact records should be restricted to Users who login to a secure web page to access a Data Form.

The Data Form Window

On the Admin menu, click the Data Forms link.  A screen displays existing saved forms.  Click the New Button to create a new form.

1 The @BRT.DataHelper() is used add links to Pages and Layouts to launch the data form in a browser

2   A descriptive Title for the form

3   The View that defines the fields to be presented on the form.  See below for details regarding <Relationship> fields included in the View.

4   The Template to be used for styling the View.  (Templates configured on the Reg Menu -> Design Templates)

5   The email notified when a form is submitted by a web user

6   The confirmation text presented to the user following a submittal

7   The target URL following submittal.  This must begin with 'http' or 'https' and include a complete URL. To add the record Id to the URL use  [[ConfirmId]] to insert the record Id.

8   The header and footer content for the form

9   Add a Captcha field to the form (recommended)

  10   Inactive? Yes to prevent use of the form

  11     Emailable? Yes to enable the form to be sent via the Brick River Email blaster

  12     RunAs - the User account to be used when unauthenticated users complete the form.

  13     Save, Return, Actions-> Delete, and Jump to navigation to designated field.


In the screenshot above, the info area 1 displays the FormId (254) in the sample Helper:  @BRT.DataLink(254).

This Helper can be pasted in to the source code that renders the navigation bar in our page Layout.


<div id="main-nav">
    <a href="/">Home</a>
    <a href="/staff">Staff List</a>
    <a href="/about">About Us</a>
    <a href="/securepage">Secure Page</a>
    <a href="/gallery">Photo Gallery</a>
    <a href= @BRT.DataLink(254)>Link Submit a News Article</a>


When a web user clicks the link, they open the Submit News Article form.


Relationship Fields on Data Forms

Fields defined in Views using the <Relationship> element may cause a Data Form to fail if the following attributes are present in that tag:

  • Dependent="true"
  • ShowAsTable="true"

For this reason it is often desirable to create dedicated Views to be linked to Data Forms.

In the above example the News View contained the element:

<Relationship Id="Authors" Name="Authors/Owners" TableId="Contacts" ShowAsTable="true" />


In order to link the Submit News Article to the News View - it was first necessary to customize the News View with the following XML overlay:

<Relationship Id="Authors" Name="Authors/Owners" TableId="Contacts" ShowAsTable="true" Invisible="true" />

The Invisible="true" attribute prevents error caused by the ShowAsTable="true" attribute.

Other alternatives in an XML overlay are:

  • Include the attribute: ShowAsTable="false"
  • Include the attribute: Cmd=Remove to remove the <Relationship> field from the View.

Rather than customize the News View it is often preferable to link the Data Form to a View that has been specifically customized for the Data Form. 

Note that most System Content and Contacts Views have <Relationship> elements that must be customized to enable Data Forms to work

  • For Content Views, customize <Relationship Id="Authors"...> to override the ShowAsTable="true" attribute.
  • For Contacts, customize <Relationship Id="Links"...> to override the Dependent="true" attribute.


Schedule a demo and see how easy it can be

Give us 15 minutes to hear your situation and share our solution.

Schedule a demo