DFFS user manual
Every setting in the Classic DFFS configuration, tab by tab. Applies to Classic DFFS v5. New to DFFS? Start with the quickstart and the how-to for common tasks. For code, see the Custom JS API reference; to install DFFS, the installation manual.
General
Dynamic Forms for SharePoint (DFFS) turns the standard SharePoint list forms (NewForm, DispForm and EditForm) into dynamic forms: tabs, headings, fields side by side, tooltips, and rules that show, hide, require or lock fields while the user fills in the form. It runs entirely in the browser, so you need Design or Owner rights on the site to set it up, and nothing on the server.
Install DFFS with the installation manual. If you get stuck, search the Classic DFFS forum or ask a new question there.
The DFFS configuration
Open a form that has DFFS and click Edit DFFS production config in the Enhanced with DFFS line under the form. The configuration opens for that form (NewForm, DispForm or EditForm), with one tab per area of settings; this manual follows those tabs in order. Configure forms in Edge, Chrome or Firefox: the configuration does not open in Internet Explorer 11 (the forms themselves still work there).
The header has two rows:
- Top row, left: the password lock, the form menu (the form’s name and type) and the Production / Development switch (see Development mode). Right: Save, Create restore point and Cancel. The same buttons are at the bottom of the page.
- Second row: when the configuration was last saved, the DFFS version with the environment badge (see Environment settings), the Tab layout switch and who the license is for.

- Switch form opens the configuration of the list’s NewForm, DispForm or EditForm.
- Import, export and restore configurations opens a side panel; see Export, import and restore.
- Print current tab prints the configuration tab you are on.
- Environment settings; see Environment settings.
- Delete deletes this form’s configuration.
Tab layout. In the Modern layout the tabs are grouped: Custom JS, Custom CSS, Field CSS, Side-by-side settings and Expand and collapse are under Code and style, and the plugins under Plugins, each with its own row of sub-tabs. Classic puts every tab in one row, as in earlier versions. The choice is remembered in your browser and only changes the navigation.
Password. Anyone with Manage Lists permission can edit a configuration. The lock in the header shows whether it has a password: an open red padlock means none, a closed green padlock means protected. Click it to set or change the password; it is stored when you save. A protected configuration asks for the password when it opens.
- Every setting has a help icon. Click it to read about the option; click again to keep the text open so you can copy from it.
- Each form has its own configuration. To reuse one, export it and import it in the other form (see Export, import and restore), or share one configuration between lists (see below).
- Some tabs show a What’s new banner that explains the new controls. Click Got it to hide it (remembered in your browser).
- Settings that need a higher license tier than yours are shown locked, with the tier they need. Their saved values are kept, and the form skips them until the license is upgraded. Which features belong to which tier is listed under License tiers on the Classic DFFS page.
Save and restore points
Save stores the configuration. A vLookup configuration that is still open in the vLookup tab is saved first, and the “Exit setup?” dialog names it; if it has empty required fields, nothing is saved and the vLookup tab opens with a message naming the column to fix. Create restore point saves the configuration and also keeps a copy with a short description you type, which you can restore later from Export, import and restore. Restore points can be restored into any form in the same list.
Save conflicts. If the configuration was changed somewhere else while you had it open (by another user, in another browser tab, or by a restore in the Classic DFFS Admin tool), Save does not overwrite that change. It shows Your changes were not saved, with who changed the configuration and when. Click Back up your changes and Copy to clipboard to keep your version: to get it back, open the setup again and paste it under Import settings. Exit and discard changes closes the setup without saving.
Last good configuration. DFFS keeps a copy of each form’s configuration as it was before the last editing session. If the saved configuration cannot be read, the setup opens with that copy and says so: check it and click Save to replace the broken configuration. The form itself shows The configuration could not be loaded, with an Open DFFS setup button, and is hidden until the configuration is fixed (from v5.1; see troubleshooting).
Development mode
The proper way to develop a form that is in use is separate DEV, SIT, UAT and PRD sites: build in DEV, test in SIT and UAT, and copy the approved configuration to PRD with the Classic DFFS Admin tool. Column changes and test data then stay out of production. See Environment settings; this needs an Enterprise license, or Professional with the Admin tool add-on. Development mode, below, is in every tier: a lighter option for small changes on one site.
Click Development in the Production / Development switch in the header. You then edit a separate development copy of the configuration, and only you see it, in this browser session; all other users keep the production version. The second header row shows Changes only affect DEVELOPMENT mode while you are in it.
- Click Open a test window in the second header row to try the development version. The form shows a red banner while it uses it. Under a form you can also click Edit DFFS development config.
- When you are happy, export the development configuration and import it in production mode (Export, import and restore).
- Opening a new browser window takes you back to production mode.
- The vLookup configuration is shared by both modes.
- The configuration warns you when production has been saved after the development copy, or the other way round.
Development mode gives you a second configuration, not a second list. Both modes use the same list, so:
- Columns and list settings are shared. Changing a column (for example from single choice to multiple choice, adding a required column or renaming a choice) changes the production form at once.
- The data is shared. Items you create or edit while testing are real items in the production list. Users see them, and flows, workflows and DFFS e-mail actions run as normal when they are saved.
Use development mode for layout, rules, tooltips and custom JS / CSS on a form that is in use. For column changes, or tests with data that must stay out of production, use separate environments.
Form builder
The Form builder tab (called Tabs in earlier versions) builds the form. Tabs split the form into pages; each tab lists the fields, headings and HTML sections it shows, in order. A tab with no fields shows no fields; to show every field, use Add ALL fields. (Before v5.1 an empty tab showed all fields; configurations saved before v5.1 keep doing so, see A tab with no fields shows all fields.) More tab settings (remembering the selected tab, tabs in rows, previous/next buttons) are in the Miscellaneous tab.
Single page form (no tabs), at the top of the tab, builds the form as one page. DFFS uses a single tab (it creates one if you have none) and hides the tab row on the form; side-by-side fields, headings and HTML sections still work. It is saved as a normal one-tab configuration with the tab row hidden, so older DFFS versions show it the same way. If you have more than one tab, remove the extra tabs first.

Tab settings
Each tab is a card. Click its header to expand or collapse it; a collapsed card shows the tab’s name and status pills.
| Setting | What it does |
|---|---|
| Tab unique ID | A name for the tab, used to show, hide or select it from rules and code. Letters and numbers only. Use it instead of the tab’s index, which changes when tabs are moved. |
| Tab name | The label on the tab. Text or HTML; can be translated with MUI. |
| Tab title | Text shown when the mouse is over the tab. Plain text, MUI supported. |
| Tab color override | A colour for this tab: a name (red), hex (#ff0000) or rgb(255,0,0). |
| Which groups can see this tab? | Only members of the selected SharePoint groups see the tab. Leave empty for everyone. Membership must be direct: a user who is only in an Active Directory group inside the SharePoint group is not recognised. |
| Click function name | Comma-separated names of functions in Custom JS to call when the tab is selected (without parentheses). Each receives the tab’s unique ID. |
| Hide this tab in | Removes the tab from NewForm, DispForm or EditForm. Useful when you copy one configuration to all three forms. |
| Show this tab in mobile or desktop browsers | Both, desktop only or mobile only (see Mobile). A tab left out of a mode cannot be shown there by a rule. |
| Note to self | Your own notes; not shown in the form. |
// Custom JS: called when a tab with "Click function name" = onTabClick is selected
function onTabClick(tabId) {
console.log("Selected tab: " + tabId);
}
Fields, headings and HTML in a tab
Under Form content you build the content of the tab from top to bottom. Drag an element by its grip handle to move it, or change the order number in front of it.
Add field adds a list field. A field can be in several tabs but only once per tab. In a list with content types, all fields are offered, but the form only shows the fields of the selected content type.
Group ID (on fields, headings, HTML sections and table rows) gives several elements the same group name, so a rule can show or hide them together: use tabGroup_YourGroupID in Visible / Hidden headings or elements. A group affects its elements in every tab.
Side-by-side index puts fields on one line: give the fields the same number (for example 1 for the first group, 2 for the next). Label position places each field’s label, and Heading ID moves a heading from the same tab above the side-by-side group. The settings that apply to all groups are in Side-by-side settings. A group fills the width of the form (at least 785 px) and its fields share it evenly; inputs, dropdowns, multiple-lines fields and people pickers fill their column, and a hidden field gives its space to the others. To set a field’s width, see Styling.
Add heading and Add HTML section add text or HTML between the fields. Both accept MUI and these values:
{FieldInternalName}: the field’s value when the form loads;{{FieldInternalName}}: the value, updated as the user edits the field.{var:name}and{{var:name}}: a global variable from Custom JS, once or kept up to date.- The live versions wrap the value in a
<span>, so do not use them inside a link. - Field values put into a heading or HTML section are cleaned first: HTML is kept, but script tags and event handlers in the value do not run.
The difference between the two is expand/collapse: an HTML section collapses together with the heading above it; a heading starts a new collapsible section.
CSS or class on a heading: inline CSS, or a class name such as the built-in tabH1 and tabH2, or your own class from Custom CSS.
Expand / collapse on a heading makes the fields below it collapsible, starting expanded or collapsed. Off collapses the heading itself with the previous heading. More settings are in Expand and collapse. Do not put two headings directly after each other and hide one with a rule: the hidden one would then control the fields below it.
Add table row adds a form row of your own, with a label (left column) and a body (right column), both text or HTML. It lines up with the fields and is included when the tab is e-mailed or printed.
<input type="button" value="Copy the address" onclick="copyAddress();return false;">
Add ALL fields adds every field in the list to the tab.
Tab controls and finding things
- The … menu in a tab card’s header has Copy (to the clipboard), Clone, Move up, Move down and Delete. Move to index is in the expanded card.
- Drag a tab card by its grip handle to reorder the tabs.
- + New tab at the bottom of the list adds a tab at the end.
- Create new tab from clipboard data (top of the tab) pastes a copied tab, in this or another form.
- Expand or collapse all tabs folds the tab cards.
- Find in tabs highlights tabs that use a field or contain a text, and finds hidden tabs and tabs that hide the Save or Edit button. Tick Hide elements that doesn’t match to see only the matches.
Rules
A rule has a trigger (a field, the selected tab, the current user, the form being saved …), a condition (operator and This value), and actions: fields to show, hide, require or lock, values to set, messages to show, e-mails to send. When the condition is met the If yes actions run. When it is not met, the rule either runs its own If no actions or, in the older mode, reverses the If yes actions.
Each rule is a card with three sections, Trigger, If yes and If no. Click a section’s banner to collapse or expand it; If yes and If no start collapsed. When the Rules tab is printed, every section is shown.

Fields that are required in the list settings are always required. To make a field required only sometimes, make it optional in the list settings and use a rule.
The Rules tab toolbar
| Setting | What it does |
|---|---|
| Disable reversing of all rules | No rule in Auto-reverse (legacy) mode is reversed. You can also turn reversing off for single rules. While this is on, new rules start in Auto-reverse mode. |
| Minimize all disabled rules | Folds the rules that are disabled. Disabled rules are dimmed and show a Disabled pill. |
| Activate or deactivate debug on all rules | Turns rule debug on or off for every rule. |
| Activate debug on all presave actions | Logs what happens when the form is saved: rules triggered by The form is saved, functions and e-mails. While this is on, the form is not saved and no e-mails are sent, so you can test safely. |
| Disable or enable all rules | Ticks or clears Disable this rule on every rule. |
| Expand or collapse all rules | Folds or unfolds every rule. |
| Create new rule from clipboard data | Paste a rule copied with Copy (in this or another form). |
| Find in rules | Click the heading to open the search controls. Highlight rules that use a field or contain a text, in the trigger part, the action part or both; rules that hide the Save, Cancel or Edit button; rules that stop other rules; rules that use Set field value. Turn debug on all highlighted rules does what it says. Tick Hide elements that don’t match to see only the matches. |
Rule order
Rules run from the top (lowest index) down when the form loads. A rule can only read the result of rules above it in Linked rules and functions, so put those first. Rules with the trigger The form is ready always run last, wherever they are in the list.
Reversing
This is the Auto-reverse (legacy) mode, the only mode before v5 and the mode existing rules keep. For field triggers, a rule whose condition is not met undoes its actions:
- required fields become optional, and optional fields required;
- visible fields become hidden, and hidden fields visible (the same for headings and other elements, and for tabs);
- editable fields become read-only, and read-only fields editable;
- a button the rule shows or hides gets the opposite state.
Set field value, Run these functions and Alert this message are never reversed. E-mails queued by the rule are taken off the queue. The group membership triggers and Logged in user is NOT the author are not reversed either. Turn reversing off for one rule with No reversing of this rule, or for all rules in the toolbar. When you write one rule for each value of a field, turn reversing off on each of them, or they undo each other.
Explicit “If no” actions
The green If yes banner of each rule has a When NOT matched switch:
- Auto-reverse (legacy): when the rule does not match, its actions are reversed automatically.
- Explicit “If no”: the rule gets its own If no section, with the same actions as If yes. When the rule does not match, those actions run exactly as configured; nothing is reversed. Unlike reversing, this can also set field values, run functions, show messages and send e-mails. An empty If no section does nothing.
New rules start in Explicit “If no” mode (in Auto-reverse mode if Disable reversing of all rules is on). Existing rules keep their mode, so one form can use both. No reversing of this rule and Disable reversing of all rules only apply to rules in Auto-reverse mode.
Explicit “If no” is not offered for rules that can never be false: The form is saved, The form is initiated and The form is ready without linked rules. With linked rules, a The form is saved rule runs its If no actions (e-mails, functions, set field value) when the linked rules are false.
Rule settings
| Setting | What it does |
|---|---|
| Index | The number in the rule card’s header. It is the run order and changes when rules are moved. |
| Rule friendly name | The rule’s name, used to refer to it from other rules and from code. Prefer it to the index. |
| Disable this rule | At the top of the expanded rule. The rule does not run. A disabled rule counts as true when another rule checks it as a linked rule. |
| Debug this rule | Shows a log under the form each time the rule runs: what triggered it, the values compared, the linked rules and the result. Use it to find out why a rule does or does not fire. At the top of the expanded rule; a rule with debugging on shows a red Debugging pill. |
| Note to self | Your own description of the rule. |
Triggers (If this trigger)
A field as the trigger checks the condition when the form loads and every time the field changes (see Validate on). Choice and lookup fields offer their values; separate several values with | to match any of them. Date fields accept [today] or {OtherDateField}, with an offset such as [today]+14. People fields accept {currentUser}. The help icon next to the trigger explains the selected field type.
The other triggers:
| Trigger | Matches when … (This value) |
|---|---|
| Selected Tab Index / Tab unique ID | the user selects one of these tabs, by index or unique ID, separated with |: 1|3 or baseInfo|communication. Checked each time a tab is selected. |
| Custom JavaScript function | the named function in Custom JS returns true. Prefix with ~ to match on false. Checked on load, or when evaluated from another rule or from code. See the API reference. |
| Workflow status (BETA) | a workflow status column has one of the values: WorkflowColumn:2|5. SharePoint 2013 workflows must set their status with Set Workflow Status; SharePoint 2010 workflows use numbers: 0 not started, 1 failed on start, 2 in progress, 3 error, 4 stopped by user, 5 completed, 6 failed on start (retrying), 7 error (retrying), 8 view query overflow. |
| Linked rules and functions | the rules and functions in Linked rules and functions are true. The operator and value are not used. |
| No trigger (must be triggered manually) | never by itself: the rule runs only when another rule runs it (Run these functions / evaluate these rules) or from code. |
| SharePoint group membership: logged in user is member of group | the user is a member of one of the groups, by ID or name, separated with |. Checked on load; not reversed. |
| … logged in user is NOT member of group | the user is in none of the groups. Checked on load; not reversed. |
| … can view membership in group | the user can see the group’s members, which also covers membership through an Active Directory group inside the SharePoint group. The group must be set to Who can view the membership of the group = Group Members. Site administrators can always view membership, so this does not work for them. |
| Azure Active Directory (Azure AD): logged in user is member of group | No longer works, and is marked so in the rule editor: SharePoint Online no longer issues the token it used, so a rule with this trigger never matches. Add the Azure AD group to a SharePoint group, set Who can view the membership of the group? to Group Members, and use … can view membership in group instead. |
| Logged in user is selected in people picker field | the user is in the named people field (Author and Editor also work). Checked on load. To react to changes too, use the people field itself as the trigger. |
| Logged in user is NOT the author of this list item | someone other than the item’s creator opens the form (DispForm and EditForm). Not reversed. |
| URL Query string key equals | the URL has Key=Value, or Key={FieldInternalName} to compare with a field. |
| The form is initiated | always, before the other rules. Place it first to set the starting state (for example the default required or read-only fields). |
| The form is ready | always, after the form has loaded and all other rules have run, so it wins over them. |
| The form is saved | the user saves. Only Set field value, Run these functions and Send or stop these E-Mails are used. A linked rule that is false skips these actions but does not stop the save; to stop a save, use dffs_PreSaveAction. |
Operator and value
The operators offered depend on the trigger: is equal to, is not equal to, is greater than, is less than, is greater than or equal to, is less than or equal to, begins with, contains, does not contain, is between and is not between (value as min:max, for example 100:200), is changed, is changed from initial value and validate with custom function. An empty value with is equal to checks for an empty field.
- is changed fires on every change to the field; is changed from initial value fires when the value differs from what it was when the form opened. Both work on field change only, not in DispForm, and ignore This value.
- validate with custom function calls the function named in This value with the field name and its value. Return
truewhen the value is valid. When it returnsfalsethe rule’s actions run (typically Display this message) and the form cannot be saved until the value is valid.
// Custom JS: "validate with custom function", This value = phoneIsValid
function phoneIsValid(fin, value) {
return /^\+?[0-9 ]{8,15}$/.test(value);
}
Validate on (field triggers only): Form load and field change, Form load or Field change.
Linked rules and functions
Adds more conditions: the rule only matches when its own condition and the linked rules or functions are all true.
- Use rule friendly names (or indexes) and names of functions in Custom JS. A function gets the rule’s friendly name and must return
trueorfalse. ,means AND,|means OR, and AND is evaluated first. Use parentheses to group. Put~in front of a name for NOT.- On load, linked rules must be above the current rule (they must have run). On field change, DFFS uses the last result of each linked rule and calls the functions again.
- A disabled linked rule counts as true.
Rule1,Rule2,Rule3|Rule4 (Rule1 AND Rule2 AND Rule3) OR Rule4
(Rule1,Rule2),(Rule3|Rule4) (Rule1 AND Rule2) AND (Rule3 OR Rule4)
IsManager,~IsClosed IsManager AND NOT IsClosed
Let linked rules evaluate the parent rule on change: when one of the linked rules changes result, this rule is checked again. Without it, the rule is only checked when its own trigger fires.
Override reversing, stop and jump
No reversing of this rule (rules in Auto-reverse mode): the actions run when the rule matches and are left as they are when it does not.
Stop if this rule = true, and jump to (on load only): when the rule matches, the rules below it are skipped, either all of them or up to the rule you name (index or friendly name). Skipped rules cannot be used as linked rules by later rules. If the rule you name does not exist, the form shows a configuration error once and stops at this rule, as if no rule was named.
Disable this rule in
Turns the rule off in NewForm, DispForm or EditForm, for when you copy one configuration to all three. A rule disabled this way cannot be used as a linked rule in that form.
Actions
The actions below are in the If yes section, and in the If no section of a rule in Explicit “If no” mode. Field lists use Add field; Add Group ID adds every field with that Group ID. The copy icon next to a list copies its fields; the icon then turns into a paste icon, and clicking it on another list (in any rule) pastes them.
| Action | What it does |
|---|---|
| Optional fields | make the fields optional (not for fields required in the list settings) |
| Required fields | make the fields required |
| Visible fields | show the fields |
| Hidden fields | hide the fields. An empty required field is not hidden, so the form can still be saved |
| Editable fields | undo read-only |
| Read-only fields | show the fields as text. An empty field that is required stays editable. Number and currency fields show their number format: the field’s decimals, the site’s digit grouping, % for percentages and the currency symbol (see currencyLcid); the saved value is not changed |
| Visible tabs / Hidden tabs | show or hide tabs, by unique ID or index, separated with commas |
| Visible headings or elements / Hidden headings or elements | show or hide headings, HTML sections and table rows by unique ID, groups by tabGroup_GroupID, side-by-side labels by their label ID, any element of the page by its id, or elements by class (.className). Separate with commas. A variable works too: {var:hiddenElements}. Do not hide a field this way; a hidden invalid field can make the form impossible to save |
| Save item / Cancel / Edit item button visibility | Not set, Visible or Hidden. Save and Cancel apply to NewForm and EditForm, Edit item to DispForm |
| Run these functions / evaluate these rules | call functions from Custom JS or evaluate other rules, by name, separated with commas; each function gets this rule’s friendly name. Or start with {inline} and write the code here. The results do not affect this rule (use linked rules for that). See the API reference |
| Display this message | show a message: under the trigger field if the trigger is a field (so do not hide that field), otherwise above the form. Text or HTML, with {FieldInternalName} values and MUI |
| Alert this message | show the message in a dialog. Write Title[#]Message for a title. The DFFS dialog does not stop other code from running; tick Use default browser alert box for the browser’s own alert, which does but shows plain text only. If the rule runs again while its alert is open (on load and as a linked rule, for example), the same message is not shown twice; a different message from the rule replaces it |
| Send or stop these E-Mails | queue e-mail templates (from the E-Mail and Print tab) by ID, separated with commas. They are sent when the form is saved and taken off the queue if the rule is reversed. stop:TemplateID stops a pending e-mail |
| Select this tab | select a tab, by index or unique ID |
| Set field value | see below |
With an Essentials license, Display this message, Alert this message, Send or stop these E-Mails, the button visibility actions and the Custom JavaScript function trigger are locked: they need Professional. Run these functions / evaluate these rules can still evaluate other rules, but not call your own functions.
Dialogs from rules
For more control than Alert this message gives (your own buttons, input fields, a callback), let the rule run a function that opens a dialog with spjs.dffs.alert or spjs.modal.add. Close it with spjs.dffs.closeDlg().
Stopping a pending e-mail
An e-mail with a send date or a recur interval waits in the DFFS_EMail list until it is sent. stop:TemplateID in Send or stop these E-Mails marks the pending e-mails of that template for this item as stopped, for example to cancel a “task is overdue” reminder when the task is closed. This only works when e-mails are sent through the DFFS_EMail list, since only that method can send later.
Set field value
Writes values into fields when the rule matches, or, in an If no section, when it does not. Never reversed. Add field, then type the value. Multiple choice fields take several values separated with |. Nothing is set in DispForm.
| Value | Result |
|---|---|
Some text | the text |
{FieldInternalName} | the value of another field (not {ID} in NewForm) |
{timestamp}, {timestamp[dd.MM.yyyy HH:mm]} | the current date and time, optionally formatted: yyyy yy MMMM MMM MM M dddd ddd dd d HH hh mm ss am/pm |
{currentUser}, {currentUserEmail} | the user’s name, or a mailto link |
{currentUser:Name} | the user’s login name, for setting a people field |
{currentUser:EMail}, {currentUser:Department} … | any field from the site’s user information list |
{userProfile:Property} | a user profile property. Run spjs.utility.userProfile() in the browser console to see them all |
{url:Key} | a value from the URL |
{var:name} | a variable from Custom JS |
[today], [today]+14, [today]-1 | a date, for date fields |
[today]#06:00, [today]+1#14:30, [today]#now | a date and a time (24-hour), or the current time |
prepend:…, append:… | add the text before or after the field’s current text (text fields). \n is a line break in plain text, <br> in rich text |
calc:{Price}*{Quantity} | a calculation with + - * /, worked out from left to right, without parentheses. For anything more, use a function |
true / false | a Yes/No field |
Only if the field is empty leaves a field that already has a value unchanged.
prepend:{timestamp[dd.MM.yyyy HH:mm]} {currentUser}: \n
Rule controls
- The … menu in a rule card’s header has Copy (to the clipboard; paste it with Create new rule from clipboard data), Clone, Move up, Move down and Delete. Move to index is in the expanded card.
- Drag a rule card by its grip handle to change the order.
- + New rule at the bottom of the list adds a rule at the end. Hover between two rule cards to show a round + that inserts a rule there.

Code and style
The Code and style tab groups Custom JS, Custom CSS, Field CSS, Side-by-side settings and Expand and collapse, each in its own sub-tab. In the Classic tab layout they are separate tabs. Custom JS, Custom CSS and Field CSS need a Professional license (see tier locks).
Custom JS
JavaScript for this form. Everything you can call and the hooks DFFS calls are in the Custom JS API reference.
- Load these files before executing the Custom JS: one path per line, absolute or relative.
~siteand~sitecollectionmake the path relative to the current site or site collection. Put#in front of a line to skip it. Verify file paths checks that each file exists. - Files are loaded with RequireJS. An AMD module gets the file name as its module name; write
moduleName|pathto choose another. Add{inject}after a path to paste the file’s contents into Custom JS instead (useful when a file will not load as a module, or to avoid caching). - Load a language file by the user’s language:
~site/i18n/texts_{currentUICultureName}.js;{currentCultureName},{currentLanguage}and{currentCultureLCID}also work. Load a default file first as a fallback.
The code editor (ACE) highlights the code. Its toolbar has format and view options, font size, key bindings and full screen. Right-click in the editor for Undo, Redo, Select all, Find / Replace, Format, Fold, line wrap, Split editor (the same code side by side, to work in two places at once), Full screen, Copy and Paste.

Custom CSS
CSS for this form, with a list of CSS files to load first that works like the JavaScript file list. Use the browser’s developer tools (F12) to find the elements to style; the styling page lists the classes DFFS uses. Your Custom CSS wins over DFFS’s own colours, including the blue of the selected tab, checkboxes and buttons.
Field CSS
CSS for single fields, applied to both the label and the value cell of the field’s row, for example background-color:#f3f6fb;. Get CSS configuration from shares the setting between forms, as for tooltips. For styles that apply to many fields, use Custom CSS; the styling page has examples.
Side-by-side settings
Settings for all side-by-side groups (you place the fields in the Form builder). The first field of a group holds the row for the others.
- Stretch side-by-side fields over both form columns: the group uses the label column too, and the group has no label of its own.
- Custom labels (stretch off): give a group, or several groups (SBS-index
1,2), a label of your own in text or HTML. SBS-LabelID names the label so rules can show or hide it.
Expand and collapse
Settings for headings that expand and collapse the fields below them (switched on per heading in the Form builder):
- Expand or collapse each section individually: off, opening one section closes the others (accordion); on, each section opens and closes on its own.
- First form section in each tab expanded.
- Heading CSS style or Class: style for all collapsible headings, inline CSS or a class such as the built-in
accordionHeading. - Exclude these headings: comma-separated heading IDs that collapse together with the section above them. An excluded first heading in a tab stays visible.
Mobile
Enable mobile support for this form gives phones a simpler layout, detected from the browser:
- every field in one column, with the label above the field;
- no side-by-side;
- no tab row when only one tab is left for mobile;
- no Enhanced with DFFS line.
Choose per tab whether it shows on desktop, mobile or both (tab settings). Hide form menu banner in mobile browsers removes SharePoint’s ribbon area. In Custom CSS, prefix selectors with .dffs-desktop-mode or .dffs-mobile-mode to style one layout only:
.dffs-mobile-mode .ms-formbody input { font-size: 16px; }
Tooltip
Adds an information icon to fields; clicking it shows your text. Enter the text or HTML per field, as one line (use <br> for line breaks). Write Title[#]Text to give the tooltip a title. MUI is supported.
- Path to custom image for triggering the tooltip replaces the icon;
~site,~sitecollectionand~parentsitemake the path work when the site is saved as a template. - Tooltip background color: name, hex or rgb.
- The tooltip sizes to its text, up to 550 px wide, and stays inside the window: near the right edge it opens to the left, near the bottom above the icon. It closes when the page scrolls. (Before v5.1, long text needed a
<div>with a set width.) - For a tooltip in a heading or HTML section, put
{tooltip:your_id}in its text, then addyour_idas an item ID with the tooltip text.
Get tooltip configuration from lets forms in the same list share one set of tooltips. Edit them in the form they come from. Picking another form and then the current form again copies that form’s tooltips into this one.
Fields and list settings
Lists every field in the list with its display name, FieldInternalName, type and whether it is required in the list settings. Use the FieldInternalNames in rules and code. From here you can open a field’s settings, add a new field to the list, or open the list settings.
Miscellaneous
Settings for the form as a whole, in collapsible groups. Expand all / Collapse all opens or closes every group; the groups you leave open are remembered in your browser. Some settings apply to one form type only, as noted. The password is set with the lock in the header (see Password).

Access and security
- Enter setup button: show the Edit DFFS config link under the form only to these user IDs or SharePoint groups. Take care not to lock yourself out; a password is usually the better choice.
- Bypass all rules for these user IDs or SharePoint group names / IDs: for these users no rules run, which is useful for administrators who must reach every field. Notification alert when bypassing rules is shown to them so they know. Custom JS can check
spjs.dffs.data.bypassAllRules.
Saving and item flow
Save and redirect adds a second save button, labelled as you choose, next to the standard one. The list needs a _DFFSID column (button next to the setting).
- In NewForm: after saving, open a new NewForm (to add another item), the saved item’s DispForm or its EditForm. Optionally ignore this when the item is added from vLookup.
- In EditForm: keep the EditForm open, or go to DispForm.
- Don’t hide this button when using the hide save button in tabs or rules keeps it visible when Save is hidden.
To redirect the standard Save button instead, use spjs.dffs.redirect in Custom JS.
Return to DispForm options: Launch EditForm in a dialog from DispForm, and Return to DispForm when editing an item and NOT opening the form in a dialog.
Check out list items (EditForm): Require list items to be checked out before they can be edited. The list needs a Yes/No column named CheckedOut with the default value No; the button next to the setting adds it. The labels are yours to change: the message shown when someone else has the item ({CheckedOutTo} inserts their name), the confirmation before checking out (leave empty to check out without asking), and the Keep checked out after save option (leave empty to hide it).
Form layout and tabs
- A tab with no fields shows all fields (from v5.1): when ticked, a tab with no fields, headings or HTML sections shows every field in the form; when not, it shows none. Ticked in configurations saved before v5.1, so they work as before; not ticked in new configurations.
- Hide tab row: use when the form has no tabs (or tick Single page form in the Form builder).
- Show this text above the tabs: a banner, with
{FieldInternalName}values and MUI. - Remember selected tab: reopen on the last tab the user had open, per list item.
- Preserve the selected tab index when navigating from DispForm to EditForm.
- Preselected tab index: the tab that opens first.
- Split tabs in multiple rows: number of tabs per row.
- Show orphan fields in a separate tab: fields that are in no tab get a tab of their own, for everyone or for the user or group IDs you list. Useful while building the form.
- Scroll to first visible form element in NewForm and EditForm.
- Previous / next tab navigation: buttons to move between tabs, with your own labels (MUI supported).
- Freeze tab row (experimental): keep the tab row in view when the form is scrolled.
- Hide the quick launch (left menu) when opening a form.
- Form background color for the label column and the value column.
Fields and form elements
- Show list of empty required fields when attempting to save the form: a banner lists the empty fields, and clicking one opens its tab and points to it. The banner disappears when every required field is filled. Set its label in Label for required fields banner (MUI supported).
- Read-only fields: show the field description for read-only fields, and style them with a border, a gray background or a shaded background, plus your own CSS.
- Multiple-choice columns in multiple columns: spread the checkboxes or radio buttons of a field over a number of columns.
- Multi lookup columns: arrange the two boxes of a multi lookup above each other instead of side by side.
- Open attachments in new tab.
- Hidden fields: fields listed here are always hidden. Neither a tab nor a rule shows them; only code that removes their
spjshiddenclass can.
Dialog (modal form)
- Dialog position and size: fixed top position, and minimum height and width in pixels, for forms opened in a dialog.
- Override delete item function when an item is opened in a modal dialog: when an item opened in a dialog is deleted, SharePoint reloads the page behind the dialog. Tick this in DispForm and EditForm to stop that reload.
Note to self (your own notes) is always at the top of the Miscellaneous tab, outside the groups.
Loading and maintenance
- Defer loading of DFFS (ms): wait before DFFS starts, if for example people pickers are not ready when your rules run.
- Toggle visibility of the configuration lists in all site contents: show or hide DFFS’s own lists in Site contents.
E-Mail and Print
Buttons that e-mail or print the selected tab, and e-mail templates that rules send. Needs a Professional license (see tier locks).
How e-mails are sent
DFFS sends e-mail in one of two ways:
- Directly (SharePoint 2013 and later, the default): sent at once through SharePoint. Recipients must be users in your organisation; external addresses work in Cc only for the E-mail active tab button. No send date or recurrence.
- Through the DFFS_EMail list (Use custom list with workflow to send E-Mails): DFFS adds an item to a list named
DFFS_EMail, and a Power Automate flow or SharePoint workflow that you set up sends it. Needed for external recipients, for a send date and for recurring e-mails. See the DFFS_EMail list. Add the_DFFSIDcolumn too (button provided) so links in e-mails sent from NewForm point to the new item.
E-mail the active tab
Enable E-Mailing the active tab adds a button that e-mails the fields of the selected tab. Limit it to some tabs with their unique IDs. Prefill To and Cc ({PeopleField}, {currentUserEmail} or addresses, separated with commas), add an e-mail header and footer, and change the labels in the send dialog. Elements with the class dffs_noEmail are left out of the e-mail.
Print the active tab
Enable print of the active tab adds a print button, for some tabs or all, with a print header and footer. Elements with the class dffs_noPrint are left out.
E-mail templates
Templates are sent by rules (Send or stop these E-Mails) when the form is saved, or from code with spjs.dffs.processEmailTemplate('TemplateID'). Each template is a card with a … menu (copy, clone, move, delete); drag a card by its grip handle to reorder, and add one with + New email.
| Field | Content |
|---|---|
| E-Mail Template ID | the name rules use; unique in the form |
| To, Cc, Bcc | addresses, {PeopleField}, {currentUserEmail}, {usergroup:Group name} (everyone in a SharePoint group whose members are visible to everyone) or {var:name}, separated with commas. Bcc works when sending directly or through a Power Automate flow, not with a SharePoint Designer workflow |
| Subject, Body | text or HTML with {FieldInternalName}, {var:name} and MUI. In the body, {viewitemlink} and {edititemlink} insert links to the item. A line break you type becomes <br>; write HTML as one line. Field values in the body are cleaned: script tags and event handlers in them do not run |
| Send date | DFFS_EMail list only. Empty sends now; [today]+5 or {DueDate}-1 waits until that date |
| Recur interval | DFFS_EMail list only. Days between repeats of the e-mail |
| Notification when e-mail has been sent | a short message shown to the user |
If To resolves to nobody, the save is stopped with a message that offers to skip the e-mail. Each template is sent once per visit to the form.
Plugins
The Plugins tab groups the built-in features that started as separate plugins: vLookup, SPJS-Lookup, Autocomplete, Cascading dropdowns and Resource Management, each in its own sub-tab. vLookup and cascading dropdowns are set up in their sub-tabs; SPJS-Lookup and Autocomplete in Custom JS (their sub-tabs link to the instructions). The plugins need a Professional license. See Built-in features for the full setup of each.
vLookup
Shows items from another list (or this list) that are related to the current item, as a table in the form, and lets users add, view and edit them there: order lines, tasks, documents. Each vLookup field is a card with its settings. See the vLookup user manual.
SPJS-Lookup
Turns a single line of text field into a dropdown whose options come from a query on another list. It has no settings of its own in the configuration: you set it up in Custom JS with spjs.lookup.init(…), as described on the SPJS-Lookup page. It does not run in DispForm.
Autocomplete
Turns a single line of text field or a people picker into a search box that suggests matches from a list, and can fill other fields from the chosen item. Like SPJS-Lookup, it is set up in Custom JS, with spjs.ac.textField(…) or spjs.ac.peoplePicker(…), as described on the Autocomplete page. It also works in the mobile layout. It does not run in DispForm.
Cascading dropdowns
Turns several text fields into dropdowns where each choice limits the next (country, then city, then office), from a list that holds the combinations. A form can have several sets, each shown as a card.
Resource management
Legacy: this plugin has not been updated since 2015. It may still work, but it is no longer maintained. It prevents double booking: the form cannot be saved if the selected resource (a choice, people or lookup field) is already booked in the chosen time. Optionally limits bookable times per resource with a configuration list. Not active in DispForm.
Implementation status
A checklist of what is left to do on the form. Add tasks, edit them in place, tick them off, reorder them, delete them, or clear all completed tasks; the tab name shows how many are done, for example (1/2). The list is saved with the configuration, so it travels with export, import and restore. The Note to self scratchpad, which used to be on the Help tab, is here too.

AI assistant
From v5.1. Describe a change in plain language, and let an AI tool of your choice (Copilot, ChatGPT, Claude or another) change or review the configuration of the form. DFFS builds the prompt from the saved configuration, you run it in your AI tool and paste the answer back, and DFFS checks the changes, creates a restore point and applies them. DFFS does not connect to any AI service. Needs an Enterprise license, or Professional with the AI assistant add-on. See the AI assistant for how to use it.
About / Help, export and license
About / Help
The About / Help tab shows the DFFS and loader versions, the versions of spjs-utility and every loaded plugin, links to the manuals and the forum, the ACE editor’s keyboard shortcuts, and how to write MUI text.
Export, import and restore
Open it from the form menu: Import, export and restore configurations. It opens in a side panel; close it with ✕, by clicking outside it, or with Escape.
- Export settings shows the configuration as text to copy. It shows the last saved version, so save first.
- Import settings: paste a configuration and press Import to replace this form’s configuration.
- Restore previously saved settings: lists the restore points and deleted configurations of every form in the list, to restore into this form.
Environment settings
For forms that move from a test site to production. Open Environment settings in the form menu and enter the site URL of each environment, DEV, SIT, UAT and PRD (the site only, not the list); Use current site fills in the one you are on. If the list name differs between the environments (for example MyListDEV), enter the list names too. Apply the settings to this form only, or to all forms for the list. They are saved with the configuration.
- The configuration header shows a badge with the environment it is opened in, or a neutral Environments pill when it is none of them.
- A form in DEV, SIT or UAT shows a coloured banner above the form, such as This form is running in the DEV environment. PRD forms show no banner.
- Copy a configuration from one environment to the next with the Classic DFFS Admin tool.

Separate environments keep column changes and test data out of production, which development mode does not. The environment badge and the Production / Development switch are independent: the badge shows which site and list you are in, the switch which copy of the configuration you edit in that list. You can use development mode in UAT too, for example to try a fix before you promote it.


Environment settings need an Enterprise license, or Professional with the Classic DFFS Admin tool add-on. Settings already saved in a configuration are kept on a lower tier.
License
The License tab has three cards:
- License code: with a valid license it shows who the license is for, and Change license code to enter a new code. One code covers all DFFS forms in the site; a new code takes effect when the form is reloaded.
- Your license: the tier (Essentials, Professional or Enterprise) and what it includes, the license type, the expiry date and any add-ons (the AI assistant and the Classic DFFS Admin tool), or the trial status. An online license is checked once a day; after SPJSWorks has changed your license, for example a renewal or a new add-on, click Check the license again to use the change right away (from v5.1).
- Site collection license: the challenge code to send when you order a site collection license.

Without a license code, DFFS runs as a 30-day trial with the Professional features. When the trial has ended, the configuration shows a card with Buy a license and Continue to the configuration. With the JSLink setup the license is entered on the JSLink setup page instead; with the central site it is in the central DFFS_Settings list (see the DFFS central site). To load the code from a file in every form, see below. A license problem shows as a red banner under the configuration header.
The DFFS_EMail list
Needed only when e-mails are sent through a list: for external recipients, a send date or recurring e-mails. DFFS writes each e-mail as an item in a list named DFFS_EMail; a Power Automate flow or a SharePoint Designer workflow on that list sends it.
Create the list
Tick Use custom list with workflow to send E-Mails in the E-Mail and Print tab; if the list does not exist, a button creates it. To bring an existing list up to date with the columns DFFS needs, untick and tick the setting again. The list is in the current site unless you point DFFS to another site with dffs_email_baseUrl (see the API reference). The flow or workflow is not created for you.
Sending with Power Automate
For SharePoint Online and Microsoft 365, set up a flow as described in Sending emails using FLOW in Classic DFFS (PDF). A flow can send to external addresses and use Bcc.
Sending with a SharePoint Designer workflow
On SharePoint on-premises, create a workflow on the DFFS_EMail list in SharePoint Designer. Use the platform type SharePoint 2010 even on SharePoint 2013 or later: SharePoint 2013 workflows only send to members of your organisation. The screenshots below show the complete workflow and its steps. It must respect the item’s send date and its Stop flag, which DFFS sets to stop a pending e-mail; for recurring e-mails it adds an item to the DFFS_RecurringEmail list. The Stop value is copied to an integer variable first, which works around a problem with Yes/No values in these workflows.






Recurring e-mails
Create a custom list named DFFS_RecurringEmail with a Date and Time column Date and a Single line of text column RecurInterval. Then create a workflow on it in SharePoint Designer (platform type SharePoint 2010), set up as in these screenshots.






Deleting sent e-mails
Optional: add a Delete item action after the e-mail is sent to keep the list small. Users then need delete rights on the list, or run the step as an impersonation step.
Translated text (MUI)
Any text in the configuration (tab names, headings, HTML, tooltips, messages, alerts, e-mail templates, labels) can hold a JSON object with one text per language. DFFS shows the one for the user’s SharePoint language (LCID), or default:
{"1033":"Approved","1031":"Genehmigt","1044":"Godkjent","default":"Approved"}
Use double quotes around every key and value. The language must be enabled in SharePoint. The JSON can sit anywhere in a longer text.
Choosing which configuration loads
Normally each form has one configuration. These options change that. All of them are variables or URL parameters that must exist before DFFS loads.
Share one configuration between lists
For identical lists, let their forms use one configuration by giving it a name of your own:
<script>
var dffs_formIdOverride = "Shared_tasklist_NewForm";
</script>
Use the same name in the same form type of every list (one name for the NewForms, another for the EditForms). Set the variable in a Script Editor web part above the form, or for all forms in the Custom JS on the DFFS Installer’s Loader file tab. The configuration can be edited from any of the lists. A shared configuration has no development mode: changes go straight to production.
Several configurations for one form
By link. Add FormConfig to the form’s URL; each value has its own configuration:
…/Lists/Requests/NewForm.aspx?FormConfig=Hardware
…/Lists/Requests/NewForm.aspx?FormConfig=Software
By a field’s value. With this variable, DFFS loads the configuration that belongs to the value the field has when the form opens:
<script>
var dffs_formTypeSwitch = "CaseStatus"; // FieldInternalName
</script>
The field needs a value when the form opens (a default value in NewForm). The configuration does not change while the user edits the field: save and reopen the item to get the configuration for the new value.
To edit the configuration for one value, open an item that has that value and click Edit DFFS production config, or change the value in the configuration’s URL: in the formId parameter, replace formType=Not started with, for example, formType=In progress. (The separate formType=3 parameter is the form type; leave it.)
Loading and troubleshooting
The loading overlay
While DFFS loads, the form is covered by an overlay. Set its text or HTML for each form in the DFFS Installer: Loading screen text (optional) on the Install DFFS in a form tab. To change it later, uninstall DFFS from the form, edit the text and install again; a reinstall from Review installations / reinstall keeps it. The default overlay is /SPJS/DFFS/loader/DFFS_loader_overlay.html (DFFS_loader_overlay_v5.html on the central site); if DFFS has not finished loading after 60 seconds, the overlay says so and suggests refreshing the page.
Open the configuration directly
Add GoToBackend=1 to a form’s URL to open its DFFS configuration without loading the form. DFFS_DirectToBackend.html in the DFFS folder is an example: put it on a page in the site to pick a list from the DFFS configurations and open its configuration. A list appears there once one of its forms has been configured.
Load time tracker
DFFS logs how long each step of loading takes (tabs, rules, plugins). Run spjs.dffs.showLoadTime() in the browser console (F12), or open the form with showLoadTime=1 in the URL. Use it to find what makes a slow form slow.
License code from a file
For the DFFS Installer: put the license code alone, on one line, in /SPJS/DFFS/installer/DFFS_License.txt. The installer then fills it in on the Loader file tab. Forms installed earlier get the new code when you press Save loader file there. With the central site, the license is in the central DFFS_Settings list instead (see the DFFS central site).
Tips
- Change the “You must specify a value for this required field” text:
var dffsRequiredFieldValidation = "Please fill in this field";in Custom JS (MUI JSON works too). - Load your own script or style sheet: add its path in the file list at the top of Custom JS or Custom CSS, for example
~site/SiteAssets/forms.js.
Change log
Every DFFS release, with what changed: DFFS change log.