I reworked the form and list module to hopefully fix several issues and add some enhancements. This module is based on the original DNN Form and List module, so after it's fully tested, I will offer it for free.  

To get it production-ready, I need a few volunteer testers. If interested in taking a look, send me your email, and I'll send you the user guide and install ZIP.  You must be on 10.3.3.

Here is the User Guide

BCC Forms User Guide

Nov 1, 2026 · @George

Overview

BCC Forms lets you build a data-entry form and a list of the submitted records on any DNN page, without writing code. It is a standalone module for DNN Platform 10, derived from the open-source DNN Form and List module, and this guide covers version 01.02.00.

One module instance holds one set of fields (columns) and the records entered against them. Visitors fill in the form; the same records can be shown as a sortable table, cards, your own HTML template, or an XSL stylesheet.

Requirements

Install or upgrade

1. Sign in as a host account and open Persona Bar → Settings → Extensions.
2. Click Install Extension, choose and follow the wizard.
3. To upgrade, install the newer zip over the existing one. The upgrade scripts run automatically and existing modules keep their fields, records and settings.

BCC Forms installs side by side with DNN's own Form and List module; it uses its own folder (DesktopModules/BCCForms) and its own database tables (BCCForms_*).

Getting started

A working form takes three steps: add the module, define its fields, and pick form or list mode.

1. Add the module. In edit mode, drag BCC Forms from the module list onto the page.
2. Open the configuration. From the module's menu, choose Configuration (it opens on its own page). Every setting in this guide lives there unless it says otherwise.
3. Define the fields. Under Data Table Setup, click Add New Column for each field, give it a title and a type, and save. Drag rows to reorder them; the order is the order on the form and in the list.
4. Choose the mode under Form Settings: list and form, form only, or list only (see Form settings).
5. Click Save Configuration and Return.

Field options

The field list shows each field's main options as ticks (a tick means yes, an empty box no).

Field types

Form settings

The form lays its fields out in DNN's standard two-column rows by default; a form template lets you arrange them yourself.

Appearance

Current View Options → Appearance sets what this page shows. It applies to the current page only, so the same module can show the form on one page and the list on another.

Visitors also need permission to add records: in Module Settings → Permissions, grant Create Record / Submit Form to the roles that may submit (for a public form, All Users or Unauthenticated Users). Actions as Buttons shows Add / Show Records as buttons instead of menu items.

After a submission

The thank-you text is entered in the HTML editor under Displayed text after form post.

Form templates

Turn on Enable Form Template to control the form's HTML. Use [label-for:Field Title] for a field's label and [editor-for:Field Title] for its input; any other HTML is written as is.

Click Generate Template for a starting point. It writes one DNN form row per field the form shows, marks required fields, and turns separators into section headings:

Notes:

• Fields you leave out of the template are not shown on the form.
• Restricted fields stay hidden from users who may not edit them, wherever you place them.
• When the DNN image CAPTCHA is on, and the template has no, the CAPTCHA is added after your fields automatically.
• reCAPTCHA and Turnstile always appear below the form; they need no token.
• To use your theme's grid instead, place the tokens inside its classes (Bootstrap 5, for example, needs a row around the columns). Labels line up in either case.

List settings

The list can be shown four ways, and paging, sorting, the filter, and search work the same in all of them.

List layout

Choose under List Settings → List Layout.

Only fields with Display on List appear in the table and cards. Administrators also see hidden and system fields unless that is switched off in Module Settings.

HTML template

Select an HTML template, then fill in the three boxes or click Generate starter template for a card design built from your visible fields.

Field titles are matched without regard to case. A token that matches nothing is left in the output, which makes typos easy to spot.

XSL stylesheets

Pick an XSL stylesheet, then choose a file or click Generate New to open the XSL generator and build one from an HTML template with tokens. Stylesheets written for DNN Form and List keep working; the data uses the same names.

Sorting, paging and limits

With paging on and no filter or search active, the list reads only the page being viewed from the database, so large lists stay fast. Sorting by text, number, date, or yes/no fields happens in the database too. Filters, search, calculated fields, and sorting by link or user columns use the slower path that loads all records; the results are the same.

Filter and search

• Filter statement limits the list to records matching an expression, for example, or put titles with spaces in square brackets. DNN tokens such as are replaced before filtering, so it shows each user their own records.
• Show Search Box adds a search box over the Searchable fields. Simple Search hides the field and match-type pickers.
• Show no records until Search keeps the list empty until the visitor searches.
• Search URL Paths searches link addresses instead of their captions.

Spam protection and security

Anonymous submissions can be checked by a CAPTCHA and a hidden honeypot field, and everything users type is cleaned before it is stored and shown.

Spam protection

In Module Settings → BCC Forms Settings, choose Spam protection for anonymous users. Signed-in users are never challenged.

• Site Key / Secret Key hold the keys of the provider you picked. reCAPTCHA v2, v3, and Turnstile each need their own pair, so enter new keys when you switch.
• Minimum reCAPTCHA v3 Score (0.0–1.0, default 0.5): submissions scoring lower are rejected. Raise it if spam gets through; lower it if real visitors are blocked.
• The Submit button stays blocked until the check passes, and every token is verified on the server. If the provider cannot be reached, the submission is rejected rather than let through.
• Honeypot Field (on by default) adds a field people never see, but many bots fill in. It works on its own or with any option above.

What users can enter

• Rich text is cleaned with an allowlist: formatting, lists, tables, links, and images stay; scripts, event handlers, embedded frames, and form controls are removed.
• Filter entry for markup code or script input applies the same cleaning to plain text fields for everyone; it is always on for anonymous users.
• When records are shown, any stored markup is cleaned again, which also covers imported and older data. The stored value itself is not changed.
• URL fields never become links, and captions are encoded.

Who can do what

Grant these in Module Settings → Permissions.

In BCC Forms Settings:

• Users are only allowed to manipulate their own items; limit Edit and Delete to records the user created.
• Max. Records per User caps how many records each user may add (blank = no limit).
• Two options take the Display All Columns and Edit Also Restricted Columns rights away from administrators, and Hide System Fields hides Created by/at and Changed by/at from them.

Notifications, import, export and templates

Email notifications

Under Configuration → Email Settings, the module can send an email whenever a record is added, changed, or deleted.

From, Reply-To, CC, and BCC take addresses the same way as To. When From is empty, the email is sent from the site's email address (Site Settings in DNN).

Export to CSV

Module menu → Export to CSV File. Pick a folder, file name, and delimiter (comma or semicolon). Optionally include the system fields and limit the export to records created between two dates. Values are exported as stored, without links or formatting.

Import from CSV

Module menu → Import CSV File. Choose the file and delimiter.

After importing, open Configuration to change field types (for example to Date or Integer) as needed.

Module templates

A template copies a module's fields, configuration, and, optionally, some records to new modules.

• Save: module menu → Save as Template. Give it a name and description, and set Max Records (usually 0 or 1).
• Use: a newly added BCC Forms module offers the saved templates. Choose one and click Apply, or start a new configuration.
• Templates and page exports made with earlier BCC Forms versions still import; settings saved under the old Form and List names are converted automatically.

Other module menu items: Show All Data as XML (the data the XSL stylesheets see), Delete All Records, Save Configuration as default, and Reset to default Configuration.

Troubleshooting and FAQ

Most problems come from permissions, CAPTCHA keys, or a template; when the module shows an error, the details are in Persona Bar → Manage → Admin Logs.

Does it need DNN 10.4? No, 10.3.3 works. On 10.3.x, the advanced HTML cleaner may not load because DNN 10.3 lacks one of its files; BCC Forms then falls back to DNN's older filter and logs this once. DNN 10.4 and later include the file.

Can it replace DNN Form and List? Yes, but it is a separate module: create BCC Forms modules and move data with CSV export and import. Existing XSL stylesheets keep working.

Does paging make large lists fast? Yes, when paging is on, and no filter or search is active; only the page shown is read from the database.

Where is the data stored? In the site database, in the BCCForms_Rows, BCCForms_Data and tables. Deleting a module from the recycle bin deletes its records.