Add
DFFS-Loader as a site column that can be added to any list in the
site collection.
Connect to site column
File location
Where
are all the DFFS-files located?
Select file location
Custom location
Use a relative path to the folder
where the files are located. You MUST use the prefix ~site
or ~sitecollection for the relative path to the site or site
collection root as in this example:
~sitecollection/SPJS/DFFS
Variables
Config list BaseUrl
Use {currentsite} to use the
configuration list in the current site.
vLookup config list BaseUrl
Use {currentsite} to use the
configuration list in the current site.
Resource management config list BaseUrl
Use {currentsite} to use the
configuration list in the current site.
Required field validation message (optional)
Use plain text OR if you like to have a
MUI setup, use a JSON formatted string like this:
{"1033":"Message in English","default":"Fallback for other
languages"}
Form type switch field
License - leave empty for 14 day fully functional trial
If
you have a SITE license you should leave this section empty and generate the Challenge code in the DFFS
backend instead.
License code challenge for Site or Site Collection scoped licenses
When purchasing a site or a site collection scoped license, you need to provide a challenge code so that
the license can be bound to the correct site or site collection. Ensure you run this code in the site or
site collection where you intend to use the solution.
SPJS-utility.js is mandatory, the others are optional.
Custom JS and CSS files
Custom JS and CSS
Put the files in a folder named "custom" in the location specified in "Select file location" above, and
add the name of the files in the textarea. Put each file name in a separate line.
Please note that there is no built-in error handling for these custom files. Use the developer tools in
the browser to look for errors if things does not load as you expect.