Remove Values from Form Results Utility
Centralpoint forms capture a result each time the form is submitted. These form results can be deleted in the client console, relative to any form. (Example, select form results, and you are free to delete all previously submitted forms).
This tool is designed when you have collected data (in form results), which you may need to remove WITHOUT deleting the entire form result record (Example: Should you accidentally collect credit card or social security numbers within a form, when compliance does not allow that), you may need to irradicate only those values (credit card numbers or social security numbers) from each submission made over time.
You will need to first get the GUID of the Form itself (by opening that form in the console, then selecting (from the top right drop down list (Show/Hide Properties) and copying the DATA ID for that form. You would then enter in the ID of the field, that you wish to remove. Executing this tool will remove all instances of that field (only) from all results (submissions) against that form.
Form Field Types Reference
Centralpoint Forms support 13 different field types. Here's a quick reference for the most commonly used types:
| Field Type |
Purpose |
Key Parameter |
| FormTextBox |
Single-line or multi-line text |
TextMode='MultiLine', Rows='4' |
| ExtDatePicker |
Date picker with calendar |
sourceFieldId (requires 3 components) |
| FormListBox |
Dropdown selection |
AddListItems (XML format) |
| FormUpload |
File upload control |
defaultValue stores file path |
| FormSignature |
Digital signature capture |
Width, Height (auto-creates 4 metadata fields) |
| FormEditor |
Rich text WYSIWYG editor |
Width='980' |
Key Point: All form fields require a group attribute that must be identical across all form components (HTML, Field Map XML, email templates). Mismatched group names cause silent failures.
DataSource Best Practices
DataSources consist of four components that must work together correctly:
| Component |
Purpose |
| SQL SELECT |
Retrieves data from database |
| Template Content |
Wrapper HTML, runs once at beginning |
| Item Content |
Repeating template for each record |
| Styles (CSS) |
Visual styling (prefer embedding in Template) |
Critical Rules
Rule 1: The Placeholder Requirement
Template Content MUST include: [cp:placeholders key='ItemContent' /]
Without this exact placeholder, rows will NOT render even if SQL returns data.
Rule 2: Attributes vs Standard Fields
Standard fields: name='FieldName'
Attribute fields: name='cpsys_Attributes:FieldName'
They will NOT render if called incorrectly.