Modern DFFS v1.2.16.0 has been released

[Alexander Bautz]

I have now released version 1.2.16.0 of DFFS for the Modern SharePoint – it fixes a few bugs and introduces new functionality. See the full change log here: https://spjsworks.com/changelog

Read more and get your license over at SPJSWorks.com

Post any feedback in the forum here: https://spjsblog.com/forums/forum/modern-dffs/

Alexander

[Travis Goodman]

Hey Alex, I’ve discovered a CSS issue with tab sets where “Make the tab set fixed/sticky to keep it at the top of the screen on scroll” is checked.

It’s adding a top attribute to push the tabs down 54px, but it’s only doing that for the tab row itself. This is causing the actual form content to overlap the tab row. I confirmed this issue by simply inspecting element and removing that top attribute, which put the tab set back to the top of the screen with no overlap.

To fix it for now, I’ve simply unchecked the “keep tab set sticky” option.

Attachments:

1. 

   Screenshot-2025-10-20-105449.png
   

2. 

   Screenshot-2025-10-20-105510.png
   

[Alexander Bautz]

Thanks for the feedback – it appears I have broken the sticky-behavior on the tab sets – I’ll get it fixed and release a new version.

Alexander

[Travis Goodman]

Found another issue today. I have a parent list and a child list that I have vLookup setup on.

In the vLookup configuration, I have Group By set to a Lookup column called MilestoneLookup. That has a value on every item in the child list. The grouping is not working though, it’s treating it like an object.

In yet another separate issue I noticed, I am bringing in additional columns within my lookup column. So I have MilestoneLookup and I’m also bringing in MilestoneLookup:DefaultOrder as an additional field within that same lookup. I want to use that additional field as the sorting field. It’s selectable in the vLookup config, but when I use the form it tells me that column no longer exists or was deleted, which is not true.

Attachments:

1. 

   vLookup-Config.png
   

2. 

   Lookup-Group.png
   

3. 

   DefaultOrder-Order-By-vLookup.png
   

4. 

   DefaultOrder-field-does-not-exist.png
   

[Alexander Bautz]

Sorting / grouping on an additional lookup field and showing it in the vLookup table will be fixed in the next version.

Regarding grouping on a lookup field: Are you sure it is a single select lookup field? – I think you could select a multiselect lookup in the group-by in earlier versions, but grouping on multichoice will not work.

Alexander

[Travis Goodman]

Hey Alex, sorry for the late followup, but it is definitely a single choice lookup.

[Alexander Bautz]

Try removing the field from the config and then add it back. If the problem persists I need some more screenshots of the list settings for that field and for the DFFS Config to try to understand what is causing it.

Alexander

[Author]

Posts