v1.0.51.0 – February 15, 2024

Bugfixes

• Fixed a bug where when using the Modern DFFS Formpage web part to show a DFFS form in a site page you got an error when opening a form in dispform and then clicking on the edit button. The form would not open.

v1.0.50.0 – February 11, 2024

Bugfixes

• Fixed a bug related to the monaco-editor used in Custom JS and Custom CSS where it did not remember the scroll position and folded code when navigating between tabs. This is fixed, but please note that the editor does not auto-resize if you resize the window after the editor is opened.
• Fixed a bug that caused the editor to sometimes fail to load (did not get past the “Loading Dynamic forms for SharePoint” message).
• Fixed a bug related to vLookup > Add new child item where you could not prefill a field that had a fieldinternalname starting with an underscore.
• Fixed a bug related to using a list view web part to show a list or library in a sitepage where the new button on the list or library did not work.

Changes

• Reversed change in previous version where the version log button was moved down to the bottom of the form. It is now shown in the top banner again. When opened in a mobile device, some of the buttons in the top banner of the forms is shown under a dropdown menu to avoid truncating the menu items on small screens.

v1.0.48.0 – February 06, 2024

Bugfixes

• Fixed a bug introduced in the previous version that caused the configurator to get struck creating the configuration / license list on a new site that did not already have a license code added.

v1.0.47.0 – February 05, 2024

Bugfixes

• Fixed a bug that sometimes caused the solution to fail to initialize when trying to open a form from a list view and throwing this error: Uncaught TypeError: Cannot read properties of undefined (reading ‘charAt’) at t.getPageContextFromLegacy
• Fixed a bug where you could get duplicates in a lookup column select when using cascading lookups on a vLookup child form.
• Fixed a bug related to setting a lookup column in a vLookup child form where it sometimes did not fill the value.
• Fixed a bug where using setFieldValue on a managed metadata (taxonomy) field did not work (introduced in v1.0.39.0 where I changed the taxonomy picker).
• Fixed a bug where the list of fields you can prefill in vLookup add new was not sorted alphabetically.
• Fixed a bug where you were unable to use the “save and exit” option when showing the form on a mobile device. The reason was that the split-button when used on a touch device did not work the same as on desktop.
• Fixed a bug when using an append field where the timestamp was off by one or more hours (due to timezone / daylight savings).
• Fixed a bug related to using quicksave or autasave in combination with append text fields where the field value was not cleared and the history did not reload to show the new value.

Changes

• Added debugging output to the console when loading the DFFS configurator in a list. You can activate it by adding an URL parameter like this: …/AllItems.aspx?DEBUG_DFFS=1 and reload the page.
• Added a callback function that lets you trigger a custom function when vLookup has loaded. Just add this to your Custom JS and change the id to match your vLookup:

function dffs_vLookup_callback(id, items){
    if(id === "vLookup_7943515991751215"){
         // Loaded vLookup with id vLookup_7943515991751215 - you can find the ID when editing the vLookup configuration    
        console.log(id, items);
    }
}

• Added a new save option in NewForm where you can save and go to editform. You can find it by clicking the down-arrow on the Save and exit button in NewForm.
• Added new functionality where when you add a new document using vLookup it will automatically open editform to let you fill in metadata on the document.
• Added new option when configuring a text field as a dropdown where you can allow “invalid values” to be able to preserve the selected value even after it has been deleted from the source list.

v1.0.46.0 – January 14, 2024

Bugfixes

• Fixed a bug related to setting a lookup column to [[item:id]] or [[fieldValue:ID]] in a vLookup child form. The value would be set in the form, but did not save to the list.
• Fixed a bug related to setting multiple lookup columns in a vLookup child form. In some cases only the first field would be set.
• Fixed a bug in the optional CustomJS function dffs_triggerSave where after adding the QuickSave functionality in v1.0.41.0 calling this function would do a QuickSave and not a SaveAndExit (triggering rules on save). This function now takes one boolean argument to set the type of save. Use dffs_triggerSave(true); to do a SaveAndExit and this for QuickSave: dffs_triggerSave(false). I have also added a fallback / default so if you have used dffs_triggerSave(); it will do a SaveAndExit after you update to this version.
• Fixed a bug related to using dffs_fieldValueHistory, dffs_beforeProperties, getFieldValue or setFieldValue in both the parent form and in a vLookup child dialog. Because of how the functions were exposed to the window namespace the vLookup child form panel sometimes overwrote the functions from the parent form – resulting in them not triggering correctly after closing the child form panel.
• Fixed a bug in the optional dffs_choice_option_hidden parameter that can be used in CustomJS. This was done fix a problem where if using this method in both the parent form and in a vLookup child form panel the child panel would override the parameter in the parent form when the child form was closed. See updated example in this forum thread
• Fixed a possible issue related to using dffs_PreSaveAction after updating to v1.0.41.0. The function will be triggered both by SaveAndExit, QuickSave or AutoSave, but there were no way to know which type of save was performed. In this version the function will be called with two arguments: exit and autosave so you can run the function only on SaveAndExit. See updated example in this forum thread

v1.0.45.0 – December 13, 2023

Bugfixes

• Fixed a bug where you got an error saving in NewForm. The item was saved, but the dialog did not close. This was related to the new feature where when quicksaving, the created / modified by and timestamps were shown at the bottom. The error was related to “itemData.Author” not existing.

v1.0.44.0 – December 13, 2023

Bugfixes

• Fixed a bug related to using setFieldValue to set a decimal number to a number field on a locale where the decimal separator is not a dot (.). This results in an error like “Only numbers are allowed” or a save error. The correct way to set a field value in a number field is like this using a proper JavaScript number format (where there are no thousands separators and the decimal separator is dot): setFieldValue(“NumberField”, 123.45);
• Fixed a bug related to hiding the save button where the dropdwn and the quick-save menu item still showed.

Changes

• Changed how numbers are shown in a number field (number and currency). It is now formatted using the currently selected locale (on the web or the user profile for the user – depending on the setting in the user profile) to determine the correct thousands separator and decimal separator.
• Added support for using negative and decimal numbers in a percentage field.
• When using quicksave or autosave, the modified date and time will update in the bottom of the form.

v1.0.41.0 – December 05, 2023

Bugfixes

• Fixed a bug were using getFieldValue on a people picker on form load returned an empty array.
• Fixed a bug introduced in v1.0.37.0 that caused a rule triggering on a boolean field to fail to trigger.
• Fixed a bug introduced in v1.0.37.0 related to setting the value from the ID column using setField in a textfield converted to a dropdown or an autocomplete. In this case the save would fail with an error like “Cannot convert a primitive value to the expected type ‘Edm.String’. This error also occurred if you used setFieldValue on a number or currency field and passed in a number and not a string.
• Fixed a bug related to number or currency fields were clearing the field or pressing in plus or minus crashed the form (minus can be used as first character).
• Fixed a bug introduced in v1.0.37.0 that caused a number field set to “Show as percentage” to save a decimal value like 0.5 for 50%.
• Fixed a bug related to document libraries were showing the field name (FileLeafRef) crashed the form. I’m not 100% sure when this was introduced but think it could be as long back as v1.0.25.0.
• Fixed a bug occurring where you had a list and a document library with the same rootfolder / URL name. In this case, the configuration would be cross-linked between the list and the library because of how the config is identified in the configuration list (using the URL-name). I have fixed this by changing how the configuration is named by appending the list template id to the name. This should not have any impact on existing configurations, but in case you are experiencing this bug you must edit the configuration and save it to rename the configuration using the new naming convention.

Changes

• Removed the margin between rows in the form to prevent extra padding when all fields inside a row is hidden.
• Added field type icon to the location field.

New features

• Added option to use a calculated field to group a vLookup table.
• Added a quicksave feature that saves the form but keeps it open. You can access this using the down-arrow on the save and exit button.
• Added an option to turn on autosave in a form. If this is turned on in the Miscellaneous tab you will see a new toggle button in the banner where you can turn on autosave. This will check for changes every 15 seconds and save if there are any changes.

v1.0.40.0 – November 22, 2023

Bugfixes

• Fixed a bug where when creating a rule with two or more conditions you could not change the root level operator from “And” to “Or”.

v1.0.39.0 – November 18, 2023

Bugfixes

• Fixed a bug introduced in v1.0.37.0 that causes the save to fail if you had a Boolean field (yes/no) in your form, if a decimal number was added to a number or a currency field or you had a hyperlink field in the form.
• Fixed a bug introduced in v1.0.37.0 that causes a single choice people picker to loose its value if you edited the item and saved it without changing the value in the people picker.
• Fixed a bug causing the search in a taxonomy field to fail to return any values. This is caused by Microsoft deprecating a method used in the @pnp/spfx-controls-react / Modern Taxonomy Picker. Until the @pnp team has updated that control to fix the problem, I have reverted to the @pnp/spfx-controls-react / Taxonomy Picker.

Changes

• Moved the edit button for a rich text editor field from the right side to the left.

v1.0.38.0 – November 14, 2023

Important

This version has a bug that causes the save to fail if you have a boolean (Yes/No) choice field in the form. I’m working on an update, but until it is ready please use v1.0.36.0

Bugfixes

• Fixed a bug introduced in v1.0.37.0 where setting a date field using a rule caused the form to fail to save with a message like “Enter a valid date between 01/01/1900-12/31/8900”

v1.0.37.0 – November 12, 2023

Important

This version has a bug that causes the save to fail if you have a boolean (Yes/No) choice field in the form. I’m working on an update, but until it is ready please use v1.0.36.0

Bugfixes

• Fixed a bug where setting a readonly datepicker to “empty” using custom js crashed the form.
• vLookup: Fixed an issue where selecting a web other than the current using the “Pick from the current site collection > Select web” treeview caused NewForm, DispForm and EditForm to fail to load. Using the “Use the fully quealified URL” worked.
• Fixed a bug where the “Empty required fields” banner would show the internal name and not the title or custom label of the field.
• Fixed a bug in multichoice managed metadata fields that caused the form to fail to save when the taxonomy field was created with spaces in the field name.
• Fixed a bug that caused a save conflict if you opened a form in edit mode and deleted an attachment and then tried to save the form.
• Fixed a bug where the highlighting of the tab on save when an empty required field is located in that tab did not work.
• Fixed a bug related to managed metadata fields where the current browser language was not added as a “Working language” in term store.

New features

• vLookup: Added options to use “Totals” where you can use sum, average or count and show it in the footer of the table
• vLookup: Added option to group the items. You can group by single line of text, single choice, single choice people picker and single choice lookup columns. If you have activated “totals” the footer is shown below each group and at the bottom for a “grant total”.
• vLookup: Added option to set max height of vLookup table before scrollbar is displayed. If you set a height and the table exceeds the set height and show scrollbars, the header and footer will be sticky and show while scrolling the body of the table.
• Lookup columns and autocomplete single line of text: Added “Suggested items length” setting where you can set the limit for number of suggested items shown when clicking on the field without adding a search term.
• Added a button to the Custom JS tab you can click to show a all fields in the current form / list.

Changes

• Added the style “align-self: center” to the formBodyWrap class.

v1.0.36.0 – October 30, 2023

Bugfixes

• Fixed a bug in datepickers where it corrected for daylight saving on dates that was not within the datespan where the daylight saving was active. This could result in an offset of the date by one hour (or whatever the daylight saving is in your region).
• Fixed a bug where you could not select an option in a dropdown choice field.
• Fixed a bug where if you added the Modern DFFS app to the APP Catalog, but did not configure any forms and therefore did not create the configuration list that holds the DFFS configurations, the New item and Edit item buttons in the banner and the menu items when interacting with a list item did not work so the default SharePoint forms was not shown.
• Fixed a bug that made it impossible to clear a datepicker using custom js like this:
  setFieldValue("Field_name", "");
• Fixed a bug where you could not clear a managed metadata field from Custom JS using
  setFieldValue("Field_name", "");
• Fixed a bug where you could not clear a lookup field from Custom JS by using
  setFieldValue("Field_name", "");
• Fixed a bug that caused the “Add dynamic content” menu to not show when configuring a custom row.
• Fixed a bug where the field label on a custom row did not use the same classname as the normal field label.

New features

• I have added a method that lets you hook into the change even on all field by adding a function in Custom JS like this:

function dffs_fieldChanged(fin, new_value, previous_value) {
    console.log("The field " + fin + " was changed from");
    console.log(previous_value);
    console.log("to");
    console.log(new_value);
}

• Added a new function you can use from Custom JS to trigger save of the form:
  dffs_triggerSave();
• Added a button to clear a datepicker when it is filled in.
• Added an option to add a custom icon before the label in a custom row to make it similar to the normal field label.
• Added option to pick a custom icon instead of the default field type icon before a field label.
• Added new option to set the width of the outer wrap of the field label placeholder for fields and custom row. Use this to override the default width for example when you set fields side-by-side.

v1.0.35.0 – October 23, 2023

Bugfixes

• Fixed an issue where when previewing an email before sending, variables added with “Add dynamic content” was shown instead of the actual value (the correct value was used when sending).
• Fixed a bug in the email body editor used to preview emails where internal links was made relative (for example link to the list item) resulting in an invalid link (relative link) in the email.
• Fixed a bug where a form in a subsite failed to load when using a single choice taxonomy field.
• Fixed a bug in the “Please fill in these required fields” message shown when saving the form without supplying a value for all required fields where fields set as required in list settings (typically the Title field) was show two times in the message.
• Fixed a bug in the tabset properties editor where toggling “Multilanguage” on and then off again would not hide the multilanguage textareas.

Improvements

• Added information about HTML vs plain text in email body below the textarea. All new lines will be replaced with <br> so if you use HTML code and use block elements you must not add a line feeds after the block element as this will give you two linefeeds in the email.
• Tidied up the actions you can choose from when triggering a rule on “After save of the form” to only include “Call a function” and “Show a message box”.
• Added option in the Miscellaneous tab to select the languages to use where multilanguage translation to reduce the list of textareas to only the ones you want and not show all available languages in SharePoint. Also changed to show the name of the language and not only the LCID.
• When resizing columns in a row, max 12 slots can be assigned. Earlier the column would be pushed down on a new line, but now you cannot assign more than 12 slots among the columns in a row.

New features

• Added option to pick link to “Current item”, “View item link” or “Edit item link” from “Add dynamic content” for use in email body.
• Added option to pick List item ID and Author from the Add dynamic content when sending an email from NewForm.

v1.0.34.0 – September 25, 2023

Bugfixes

• Fixed a bug introduced in v1.0.33.0 that caused an error “The form hasn’t been configured with Modern DFFS” when navigating from dispform to editform using the button in dispform.
• Fixed a bug introduced in v1.0.33.0 that caused an error when trying to configure a list that has no existing configurations for Modern DFFS.

v1.0.33.0 – September 24, 2023

Bugfixes

• Fixed a bug related to clearing the value in a people picker using
  setFieldValue("field_name", "");
  and then setting a different value with
  setFieldValue("field_name", "user@domain.com");
  In this scenario, the initial value would reappear and the new user would ba added to the field. Just clearing without resetting the field would work and save correctly with a null-value.
• The DFFS button in the banner was not properly hidden for users without Manage lists permissions before the user interacted with one of the list items. This is now fixed so the button does not show for users without this permission.
• Fixed a translation error for Czech and Slovak language where the Save button in the form was not translated. Please note that there are still some strings in people pickers and managed metadata fields that are not translated to Czech language. This must first be done in the @pnp/spfx-controls-react project and then it can be added to the Modern DFFS code.
• Fixed a bug that crashed the form if you on a lookup field opted to use the “Title (linked to item)” field in the “In this column” field when configuring the field in list settings. I also fixed a similar bug related to selecting ID in the “In this column”.

New features:

• Added a new feature that lets you load configurations for a form from another site in your tenant, or from a JSON-file (export the config and save it to a .json file). See more information in the user manual.
• Added option to show an icon that identifies the field type to the left of the field label. This can be toggled in the Miscellaneous tab.
• Added placeholder text for all field types that support it (shows when the field is empty).
• Added the option to also hide the Delete button and the Copy link button in the Show / hide form buttons action in a rule.

Improvements

• Optimized the initial load of the DFFS code to try to prevent the default SharePoint form to open when the user clicks on the New button or tries to open a list item in View or Edit mode immediately after the list view has rendered.

v1.0.32.0 – September 07, 2023

Bugfixes

• Fixed a bug in modal where if you add HTML code with input elements in the body where the input lost focus on every keyup.

New features

• Completed the translation of the frontend (end user facing part) to cs-cz and sk-sk. Also added translation for cs-cz and sk-sk for date pickers. The default datepicker control has many languages already built in, but not these two.
• Added support for using default SharePoint formatting syntax for column formatting and using customRowAction “defaultClick” for opening the view item form and “editProps” for opening the edit item form.
• Added showFooter option on the dffs_showModal. Set it to false to hide the footer where the buttons are. Also, the dffs_showModal now returns the ID of the modal – this can be sued to programmatically close the dialog. See instructions linked above.
• Added option to preview an email before sending. The email opens in a panel after the form is saved, and the user can edit the email and choose whether or not to send it.
• Added support for querying other site collections (in the same tenant) when using vLookup or render textfield as autocomplete or dropdown. All users must have read access to the other site collection for this to work. See contextual instructions when configuring the different components.

v1.0.31.0 – August 19, 2023

Bugfixes

• Fixed a bug in the “Render field as dropdown” (configured on a single line of text field) where the “Autofill if the dropdown only has one option” did not work.
• Fixed an additional bug in datetime fields when offsetting the date value based on the web and user time zone settings. If the user did not have a timezone set on the user, it did not fall back to using the web time zone and the date value was not properly offset.
• Fixed a bug in a lookup field with more than 5000 items where it failed with an error like “Cannot read properties of undefined (reading charAt)”.
• Fixed a bug where a lookup column that had additional fields selected under “Add a column to show each of these additional fields” in list settings would throw an error if you tried to use a filter (to create cascading lookup fields).
• Fixed a bug where when setting a people picker as readonly, only the initial value (the value it had on form load) would show. The value set in the field before it was set as readonly would still be saved even if the readonly field did not show the correct value.
• Fixed a bug related to setting a people picker by userId using setFieldValue(“NameOfField”, 123) would throw an error.
• Fixed a bug related to setting a multichoice people picker using “Set field value” on a textfield rendered using “Render field as dropdown”.

New features

• Added the possibility to add calculated columns to DispForm.
• Added support for adding a custom row with two columns (“label” and “body”) where you can insert custom text / HTML.
• Added support for adding a custom field label on a field in a vLookup configuration.
• Added partial Czech translations of the frontend (end user facing) parts of Modern DFFS. The translation is not 100% completed so some of the strings are still in English. I hope to have this updated in the next version. If you want to help translate it to your language, please contact me.

v1.0.30.0 – July 26, 2023

Bugfixes

• Fixed a bug in vLookup “add new item” where lookup field values was not properly set.
• Changed the width of the lookup field dropdown and changed the white-space wrapping to show long labels on multiple lines instead of truncating the text.
• Fixed a bug occurring when using a cascading filter on a lookup field that caused the filter query to loop –  which could cause a throttling error from SharePoint. 

v1.0.29.0 – July 13, 2023

Bugfixes

• Fixed a bug introduced in the previous version – related to offsetting dates to correct for differences between the local user time-zone and the server time-zone. The bug occurs if the user has not set a timezone on their user in Microsoft 365 and crashes the form when loading a form with date fields in DispForm or EditForm, or selecting a date from the date-picker.

v1.0.28.0 – July 09, 2023

Bugfixes

• Fixed a bug related to using getFieldValue on a date and time field. If you used the “dateObject” parameter to return a proper date object, you would get a date object with reference to the original field value so manipulating the object would change the value of the field. It now creates a new object without reference.
• Fixed the format of the date picker textarea when using date and time format to not include the time – as this is shown as dropdowns to the right of the field. I also removed the seconds from the field in DispForm.
• Fixed a bug where the time selector did not change to 12-hour format (AM/PM) when the time format of the site was changed to 12 hour.
• Fixed a bug related to using different time zones on the site and local computer where the dates would get offset by the time difference between local timezone and UTC. This happens because dates are stored in SharePoint in UTC format, and DFFS did not properly account for this behavior. Now the date value are offset with the difference between the local timezone and UTC both when you open a form to view the datepicker and when saving the item back to SharePoint.
• Fixed a bug in the vLookup table where boolean (Yes/No) fields did not show the value.
• Fixed a bug related to the banner listing the required fields when trying to save the form without filling in all required fields. The list would show all required fields and not only the ones that are empty.
• Fixed a bug where setting the attachment field as required did not work properly and you could not save the form even if you added an attachment.

New features

• Added search option in the rules configurator to let you find rules where you have used a specific field name or text in the “Note to self” text area.

v1.0.27.0 – June 25, 2023

Bugfixes

• The previous version introduced a bug that caused the form to not render (only header and footer would show) unless you had a rule that toggled the visibility of some form items.
• Fixed a bug that in some cases prevented the validation of required fields and let the form save with them empty.
• Added the Please fill in these required fields banner to the top of the form (it was originally shown only at the bottom).
• Fixed a bug in the editor where you could not select text in the Custom JS or Custom CSS editor with the mouse.
• Fixed a bug related to Custom JS Load external JS files where the external scripts would load two times when you had the Load jQuery toggle on.
• Fixed a bug related to external js files where if had a corrupt link to an external js file, the form would not render and you only saw an error message in the developer console. Now the form is rendered and you get a dialog box in addition to the error message in the developer console.
• Fixed a bug where the Rich text editor in the form configurator did not properly show the font size selected in the editor. This problem also affected Rich text fields in the form if you didn’t use the TinyMCE rich text editor (which is on by default in the Miscellaneous tab).

v1.0.26.0 – June 22, 2023

IMPORTANT: There is a bug in this version that prevents the form from showing if you don’t have any rules that show or hide elements. I’ll publish a new version during the weekend to fix this issue.

Bugfixes

• Fixed a bug that resulted in a 404 message when loading DispForm or EditForm on a form with many fields in the configuration.
• Fixed a bug where when rendering a single line of text field as a dropdown, the “Autofill if the dropdown only has one option” was not working on load.

New features

• Updated the functionality for rendering a single line of text field as a dropdown by adding option to sort the items, use pipe-separated options (like in the Classic DFFS) and set field values. See user manual for details.
• Updated the functionality for rendering a single line or multi line text field as an autocomplete search field by adding option to sort the items, use additional search fields and set field values. See user manual for details.
• Added option to use a variable in the “Add dynamic content” that can be used in different fields throughout the configuration. The variable must be predefined in Custom JS or be available by default in your SharePoint site.
• Added option to disable a rule.

v1.0.25.0 – May 29, 2023

Bugfixes

• Fixed a bug introduced in v1.0.23.0 that caused people pickers to not save changes.

v1.0.24.0 – May 28, 2023

Bugfixes

• The browser-based spell checking was disabled in the TinyMCE rich text editor – it has now been turned on to allow for spellchecking using the default spellchecker in the browser.

v1.0.23.0 – May 28, 2023

Bugfixes

• Fixed a bug where the List classic configurations was visible in the Import / Export panel even if the site did not have any Classic DFFS configurations.
• Fixed a bug introduced in v1.0.18.0 that caused the Switch form button in the configuration to stop working correctly (it would not redirect directly, but when you clicked the DFFS banner button again it opened the form you tried to switch to).
• Fixed a bug where the contents of the TinyMCE menus sometimes did not show.
• Fixed a bug where a column set to size 12 in extra large screen size and 6 in medium and large used the wrong size (6) in extra large screens.
• Removed some built in system fields from the Prefill this field dropdown in the vLookup configuration.

Changes

• Changed the initial height of the rich text editor when using TinyMCE to ensure the menu banner stays on the top when scrolling long text.
• Added information about the list and field used in the lookup column in the top of the Field properties panel.
• Changed the error message showing when the form fails to load based on a configuration error in the form from being a dialog box to showing directly on the form panel.
• Updated the SPfx framework to v1.17.2

Known issues

• There is a known issue related to the Edge browser on IPad where the the rich text editor does not work if you do not use the TinyMCE rich text editor. Turn on the TinyMCE editor option in the Miscellaneous tab.

v1.0.22.0 – May 6, 2023

Bugfixes

• Fixed a bug that crashed the dispform or editform if you had a multichoice people picker where a user account that was disabled in AD or that did not have an email address in the profile was selected.
• Fixed a bug in the email functionality where if you tried to pull To, CC or BCC from a multichoice people picker, the format of the email addresses was not correct, and the email would not be sent to the selected users (the email addresses were delimited with comma and not semicolon).
• Fixed a bug where if you toggled the Load jQuery button in the custom js to ON, but you do not have any external js-files loaded in the top of the custom js page rules triggering on-load were never triggered.
• Fixed a bug where if you had rules triggering on-load that hid sections of the form (tabs, fields, or HTML section), the form elements would show briefly before they were hidden.

v1.0.21.0 – May 3, 2023

Bugfixes

• Fixed a bug that caused the rule editor to crash when adding a Set field value action on a boolean (Yes/No) field and toggling the field to Yes.
• Fixed a bug where the ID column was selectable in rule actions where the ID column should not be selectable (like Editable fields and Set field value).
  Fixed a bug where when using append on a dropdown and first selecting “Specify your own value” before selecting an option from the dropdown the radio button was not unselected and Specify your own value input field was not set as readonly.
• Fixed a bug that could cause the page-context to not update when switching between two lists by clicking in the quick-launch. This would result in a click on the New item button or on one of the list items being registered on the wrong list – effectively opening the NewForm, DispForm or EditForm on the other list.

v1.0.20.0 – May 1, 2023

Bugfixes

• Fixed a bug introduced in v1.0.18.0 where you the first time you create a DFFS configuration for a form are presented with a default form containing all fields in the list. This form should only show the editable fields, but a lot of built in system fields that should not be editable were also shown.
• Fixed a bug introduced in v1.0.18.0 that may crash the form when trying to show the version log of a list item.
• Fixed a bug occurring when renaming a folder in a DFFS form where the name of the folder would be duplicated with a dot – like this folder_name.folder_name.
• Fixed a bug that prevented DFFS to load when showing a list using the list web part in a SitePage. Please note that to enable the Modern DFFS in a list web part you must have the command bar visible (web part properties > Show command bar).
• Fixed a bug where the Copy link button in the banner or in the ECB menu did not copy the correct Modern DFFS link but a link to the default SharePoint form. It will now open DispForm of the list item and copy the correct link.

v1.0.19.0 – April 20, 2023

Bugfixes

• Fixed a bug introduced in the previous version where a  number field where Number of decimal places was set to Automatic would cause a crash in DispForm.

v1.0.18.0 – April 20, 2023

Bugfixes

• Fixed a bug preventing save of a form after clearing a number or currency field.
• Fixed a bug where the version history on an append field showed the wrong name for the editor of individual versions (it showed the author of the list item as editor on all versions).
• Attempted to fix an issue where side-by-side fields (when using layout with multiple columns in a row) overlapped and did not properly shrink to fit when the screen was to narrow.
• Fixed a bug in the Modern DFFS Formpage web part (used when showing a form in a sitepage) where opening an item in dispform and then hitting edit would load the dispform config and not the edit form config in edit mode.
• Changed the ID attribute on the vLookup control to fix a problem where the ID started with a number. This only affects custom js or custom css if you have addressed the placeholder there.

Changes

• Added formatting of number and currency values in DispForm (using toLocaleString for the current selected locale)
• Removed the auto-reload of the page after saving an item (new or edit). This is done because reenabling DFFS after the page reloads could take a few seconds – resulting in the default form (or a message stating that the form hasn’t been configured) showing if you clicked new or edit item to fast after the reload. The downside is that it takes up to 30 seconds before the new or changed item are updated in the list view. A message is shown at the bottom of the listview after saving an item informing about this delay.
• Changed the control for the dropdown columns to allow autocomplete (type to search) in all dropdowns.

New features

• Added support for using additional fields on a lookup column in the forms. You can add these fields in DispForm as in the standard SharePoint form, but also in NewForm and EditForm (in readonly mode) to show the extra information immediately when selecting a value in a lookup column.
• Added support for “Add your own value” on choice columns.

v1.0.17.0 – April 10, 2023

Bugfixes

• Fixed a bug occuring if you had a field selected in a rule action and then deleted this field the rules tab would crash when you tried to edit the form.
• Fixed a bug where the history on a multiline text field with append would not show if you had multiple fields with append in the same form.

New features

• Added a new feature that lets you select the same tab in EditForm when you first open the list item in DispForm and then click the edit button. To use this you must create a rule in EditForm that triggers on form load and use the When navigating from DispForm, select the same tab option in the select tab action.
• Added new option to create a link to a form specifying the selected tab using the sTab URL query string parameter. See user manual for details.

v1.0.16.0 – April 04, 2023

Bugfixes

• Fixed a bug where you could not check the checkboxes on a multichoice field. This bug was introduced in the previous version.

v1.0.15.0 – March 27, 2023

Bugfixes

• Fixed a bug that caused the rule configurator to crash if you delted a field used as a trigger.
• Fixed a bug that could cause the banner buttons in a list view that was not configured with DFFS to be disabled.
• Fixed a bug where the permission check to determine whether to show or hide the edit item and delete item buttons was checking the web permissions and not the list / item permissions in case the list or list item had custom permissions.
• Fixed a bug where the function dffs_PostCancelFunction (if configured in Custom JS) was triggered when you navigated from dispform to editform of a list item.
• Fixed a bug that occurred when you used the 30 day trial and navigated from dispform to editform by clicking the edit button in dispform or if you opened a child item (vLookup or lookup). This would show a message stating that the trial period was exceeded.
• Fixed a bug where opening a dropdown choice meny when the screen size was less than 600px would crash the form.
• Fixed a bug where the Custom JS and Custom CSS editor crashed if the CDN source where the editor (monaco-editor) is loaded from was blocked in a company firewall. In case it is blocked the custom js and custom css will render as a regular textarea.

Changes

• Changed the rendering of long text in a dropdown select to let the text break on multiple lines to avoid truncating the text.
• POSSIBLE BREAKING CHANGE: I had created a custom ID for items to let you address items by id in a rule of in custom js, but had made a mistake and had the ID start with a number. This does not work when using the document.querySelector function in Custom JS. I have therefore change the format of the item id from this format: 7021728760377641_DueDate to this format: DueDate_7021728760377641 for fields, grid, rows, columns, tabset, rte and html. Please update any rules or custom js where you address items by this ID.

New features

• Added a new rule action to show or hide the Save, Edit and Cancel buttons.
• Added a new feature where you can use an URL parameter DFFSSource in the URL when you create a link to a list item using in the new Modern DFFS Formpage webpart. When using this URL parameter you can have a default redirect, but still be able to override the redirect using the function dffs_PostSaveAction or dffs_PostCancelAction. If you use the Source URL parameter (built-in functionality in SharePoint) you cannot override the redirect in Custom JS.

v1.0.14.0 – March 07, 2023

Bugfixes

• Fixed a bug where the link copied using the banner button was wrong if you used it on a child form in a panel over the current form.
• Fixed an error in the implementation of the dffs_PostCancelAction function where the function was only called when cancelling a child form (a lookup item or a vLookup item opened over a parent form in a panel).

Changes

• Updated the jQuery version that is loaded if you toggle the Load jQuery button in the Custom JS tab in your form from v3.6.0 to v3.6.3.

New features

• Added a webpart called Modern DFFS Formpage to the solution. You can add this to a modern site page in for example SitePages and use it to add, view or edit items in a list that has Modern DFFS Forms configured. To use it you must pass the list guid, form type and item id to the page in the URL query string. See instructions when adding the web part.

v1.0.13.0 – February 24, 2023

Bugfixes

• Fixed a problem with authentication where you could get a 403 / authentication failed message when saving the configuration or related to lookup / cascading dropdown / autocomplete / vLookup fields.
• Fixed a problem where you could not access the userProfile in a rule triggering on Form is loaded and you got a message stating “The user profile is not ready”.
• Fixed a bug where triggering a custom js function from a rule triggering on load did not always work because the custom js was not finished loading before the rule was triggered.
• Fixed a bug related to multiline text fields with Append Changes to Existing Text where if the last edit did not add a value in the field, the previous values / history was not shown in the form.
• Fixed a bug related to adding tabs to a tabset where if you added more than one tab in one edit only the first tab was actually created.

New features

• You can now access the currently logged in users profile in your custom js using the variable dffs_userProfile
• You can now access the vLookup dataobject using the id of the vLookup (you find the ID at the bottom of the first tab of the vLookup configuration) using this format: items_[vLookup id] – here is an example: items_5267157507130824_vLookup

Changes

• Changed the name of the rule trigger Result from another rule to Run based on the result of another rule to clarify what it does.

v1.0.12.0 – February 20, 2023

New features

• Added option to use the core TinyMCE as editor for rich text fields to add support for tables as the default modern experience editor lacks some functionality. This new editor is ON by default, but if you want to turn it off you can do so in the Miscellaneous tab for each form.
• Added new functionality for opening lookup items when clicking the link in a list view. Earlier it opened the default out of the box form, but now it will open the lookup item in a panel in the current view. Please note that you must have a configured Modern DFFS form on the lookup item list for this to work.
• Added refresh button on all vLookup tables where you can add new items to the child list.
• Added support for configuring actions for when a form is saved (after save), cancelled (after hitting cancel / close) or deleted (after the item is deleted from within a DispForm or EditForm) to let you add for example a redirect to another page. This must be done in the Custom JS tab in your form configuration. See examples here.

Changes

• Removed the currency symbol in display form if the field is empty.

Known issues

• When adding or editing child items in a vLookup, the table does not always refresh to show the changes. I haven’t been able to figure this one out yet so for the moment you must use the refresh button just above the table to do a manual refresh if necessary.

v1.0.11.0 – February 12, 2023

Bugfixes

• Fixed a bug introduced in v1.0.4.0 where multiline text fields did not show current value in displayform or editform if you did not use the append functionality.
• Fixed a bug in the dynamic content selector for timestamp where the example for “Today’s date (plus or minus offset)” didn’t use “today” in the placeholder inserted.
• Fixed a bug where you could unselect a single choice lookup item in editform, but it did not save so the option would not actually get removed.
• Fixed a bug in the vLookup table where a rich text field rendered the HTML code as text.

Changes

• Clicking a lookup item link in a display form now opens the lookup item in a side panel over the current item instead of opening it in a new tab using the default SharePoint form.
• Changed the initial placeholder when loading vLookup to a spinner.
• The rule actions for show or hide an element now allows for selecting items by class.

New features

• Added option to import from Classic DFFS by copy-pasting the exported configuration from your Classic DFFS form.
• Added option to show a single or multiline textfield as an autocomplete. See user manual for details.

v1.0.10.0 – February 6, 2023

Bugfixes

• One more bugfix on the lookup column to fix an error when using a “LookupField” (the field selected in In this column in edit column) that has a null-value (is empty).

v1.0.9.0 – February 3, 2023

Bugfixes

• Fixed a bug related to using a lookup column where the “LookupField” (the field selected inIn this column in edit column) was not the Title field. In that case editing a list item and saving caused an error.

v1.0.8.0 – January 31, 2023

New features

• Added new functionality to let you show / hide elements by ID in a DFFS rule. This can be any element in the form (get the ID by right clicking the element in the formbuilder and select “properties”) or any valid HTML element ID from the DOM. 
• For backwards compatibility (with the classic DFFS) I have added back the auto-population of an unique value if you have a field named _vLookupID in your form. The format is like this: 12:1675185443242 [userId:timestamp]. There is already an auto-population of a similar ID if you add a field named _DFFSID to your form, but in that case the format is like this: 1675185443242 [timestamp].

Changes

• I have made one internal change to the license code validation to allow for multiple site collection licenses on the same license code to make it easier to administer.

v1.0.7.0 – January 25, 2023

Bugfixes

• Fixed a bug related to the change to use the root folder name and not the list GUID in the title of the configuration. When creating a new child item from vLookup and the child list was edited with v1.0.4.0 (and therefore had the rootfolder name in the title field) you got a message box “No configuration found”.
• Fixed a bug in vLookup where setting a child list lookup field to the parent item title did not work (it looked OK in the form, but the value was not saved).
• Fixed a bug where the cancel button in the parent form stopped working after opening a vLooup child item and clicking the cancel button in that form.
• Fixed a bug with uploading documents in a vLookup configuration where a space in the document name was replaced with %20 in the file name. This caused an error when trying to open the document.

Changes

• Changed the rendering of the FileLeafRef (Document name) field when used in a vLookup table so it creates a link to the document.

v1.0.4.0 – January 08, 2023

Bugfixes

• Fixed a bug in the vLookup functionality where a multichoice lookup column or a multichoice people picker would now show in the table.
• Fixed a bug in the vLookup functionality where setting a lookup column when adding a new document to a document library did not work.
• Fixed a bug in the cascading lookup functionality (where you use a filter to make cascading lookup columns) where you got an error like this when saving the item: A primitivevalue node with non-null value was found when trying to read the value of a navigation property…
• Fixed a bug where you could get an error in DispForm or EditForm like this on a people picker field: Cannot get value for projected field AssignedTo_x005f_Department.
• Fixed a bug where the Title field was not selectable in the forms for a Tasks list (listBaseTemplate = 105). This also caused an error where you imported a Classic DFFS configuration that used the Title field.
• Fixed a bug with tabs where – if you scrolled the form – the content of the form would shine through the tabs when hovering over them.
• Fixed a bug where the chevron-down icon on the banner in the rich text editor did not show.
• Fixed a bug where a multiline text field with append (the option Append Changes to Existing Text set to yes) did not show the history from the previous edits below the field.
• Fixed a bug where a configuration imported from a Classic DFFS form would not trigger the imported rules.

Changes

• Changed so the form configuration title (in the configuration list) is no longer the GUID of the list or library, but the rootfolder name (the name shown in the URL of the page).

New features

• Added a new option to the tabset properties: Make the tabset fixed/sticky to keep it at the top of the screen on scroll.

v1.0.3.0 – December 20, 2022

Bugfixes

• Fixed a bug in the Import / Export functionality where Classic DFFS configurations for the current list did not show when your site was on a managed path (/sites/site_name).
• Fixed a bug that prevented the Modern DFFS from activating in other list templates (it only worked in the custom list template with ID 100. It will now work in 101 (document library), 103 (Links), 104 (Announcements), 105 (Contacts), 106 (Calendar), 107 (Tasks), 150 (GanttTasks), 170 (PromotedLinks), 171 (Tasks) and 1100 (IssueTracking) in addition to 100 (custom list).
  
  Please note that some of the older list templates might loose some functionality if you use a DFFS form (Classic or Modern DFFS) and not the default SharePoint form.

v1.0.2.0 – December 19, 2022

Bugfixes

• Fixed a bug on the first setup where the configuration screen would not load until you have refreshed the page.
• Fixed a bug where a rule triggering on a boolean field being Yes on load in NewForm would not properly trigger (the rule did not pick up the default value set in the list settings for boolean fields).
• Fixed a bug with triggering on a people picker on change.
• Fixed a bug in vLookup configuration where you could not pick Author / Editor or Created / Modified in the table setup.
• Fixed a bug in vLookup where setting a lookup column in a child did not work properly.
• Fixed a bug in the tabset configuration where – if you deleted a tab – the next tab would get the label from the deleted tab.

New features

• Added new functionality to import configurations from the Classic DFFS version. Please note that not all parts of the classic configuration can be imported. You must therefore test the configurations to ensure it works as expected after you have imported it. The following parts will be imported: Tabs with fields and headings / HTML, all rules (but complex linked rule configurations must be recreated). If you have not used the tabs in the Classic DFFS configuration the formbuilder will show a message telling the form has no configuration when it is reloaded after the import. The following will not be imported and needs to be reconfigured: vLookup configurations, Cascading dropdowns, Custom JS, Custom CSS, Email configurations and any Misc tab configurations.
• Added new functionality to let you export and import configurations as JSON. This can be used if you need to copy the configuration from a DEV site and into a PROD site (if you don’t just use the dev mode configurations toggle when editing a configuration).

v1.0.1.0 – December 07, 2022

Bugfixes

• Added some missing currency indicators for currency fields.
• Fixed a bug preventing you from setting a lookup field as readonly.
• Fixed a bug preventing you from configuring a vLookup.
• Fixed a bug where the custom js was not copied when you copied the config from one form to another.

Changes

• Changed the layout of the date and time field to show date and time controls on one line.

New features

• Added the ability to label a row in the form configuration.
• Added option to load external *.js files above Custom JS.
• Added option to clone a rule.
• Added new trigger: Output of another rule.
• Added ability to use a custom render function to render a single line of text field using a function created in Custom JS – see user manual for an example.
• Added ability to render a single line of text field as a dropdown based on values from another list. You can use filters from other fields in the form to create cascading dropdowns.
• Added a yellow warning in the top left corner of the configurator to remind you if you haven’t set a password on the configuration.
• Added option to create cascading lookup fields by using filters from other fields – see user manual for an example.
• Added option to render a lookup column as a treeview – see user manual for an example.

v1.0.0.0 – November 01, 2022

Initial release