November 2022: The Modern DFFS has been released and can be found here: https://spjsworks.com
May 30, 2022: I have added a screenshot of the rules-section.
Here is a long overdue sneak peek into the functionality of the new SPFx based DFFS version that I’m working on. I’m still not ready to publish it, but the form-builder with drag-and-drop placement of form elements is mostly done.
The layout is based on the Fluent UI Grid so it will have a responsive layout that adapts to the width of the screen. As you can see in the Column properties image below, you can specify how many of the 12 slots of the screen width a column uses for the different screen sizes.
This new DFFS version will be packed as a SPFx app and must be uploaded to the app catalog (tenant or site collection app catalog) by an admin.
When this is done, you will see this button in the banner of your list / library:
A click on that button lets you select NewForm, DispForm or EditForm to start configuring the list form.
You can add grid, row, column, tabsets, rich text, html and fields to the form by drag-and-drop. All elements have properties that can be changed – see example below.
Preview form – extra large screen size:
Preview form – small screen size:
Update May 30, 2022
Rule section is starting to come together – here is a screenshot:
For anyone that has used the Power Automate / FLOW it is obvious where I have borrowed some of the layout. As you can see, I have built a proper multi-condition trigger where you can check the value of different fields without the hassle of using linked rules (from the old DFFS version).
Leave a comment below if you have any feedback at this point.
16 thoughts on “DFFS Modern – Sneak peek”
Very exciting! Can’t wait
Let us know if we can help with any testing…
I’m excited to try it out after we transfer to Sharepoint 2019 and you’ll release it. Perfect, looks really cool.
This is very exciting. Looks good and I am sure will function good as well. When are you expecting to have this ready? Can’t wait to try it out.
I’m not sure exactly how long time It will take, but I would estimate at least a month before I have a first (basic) version ready for testing.
I’ll post an update within a week or two with the progress.
Fantastic, looks like a great improvement.
Will current licensees have rights to use this version or will a new license be required?
This new version will require a new license code, but current licensees will get a free upgrade.
I do however plan to introduce a 20% yearly maintenance fee (of the purchase price) for all licenses.
I have put in a lot of work over that last 10 years(!) to develop and support DFFS, and need to have a little more reliable revenue to keep up the good work 🙂
Thanks Alexander! I’ve used DFFS for years at a couple of major US banking institutions (I’m friends with both Kasey Pickar and Keith Hudson, among many other of your common blog readers/commenters). I now have my own SharePoint Online tenet.
I’d love to assist with testing your new solution when it is ready. It sounds like it may be soon!
Looking forward to the new version!!
I can’t wait to try this out on my personal SP Online tenant!
Sorry for the lack of update. I have made good progress and plan to release a first beta version next week.
I cant wait for this new DFFS 🙂
DFFS for the Modern SharePoint Experience is finally here: https://spjsworks.com
Let me know what you think in the dedicated forum: https://spjsblog.com/forums/forum/modern-dffs/
I installed the Modern DFFS package under “Manager apps” with the SharePoint admin center of my SharePoint Online version. It says it’s enabled for all sites. However, getting “Unable to locate the DFFS files!” when clicking on the DFFS icon in the ribbon of the List therefore not sure I installed it correctly. BTW – I still have the classic DFFS version installed on my SharePoint Online version. Any assistance would be appreciated since interested in testing and learning the Modern DFFS version.
Could you please post a screenshot of the actual error message you are getting? – I’m not sure, but I had another user report something similar and it was caused by an error in the CDN configuration on the tenant. You can find more information about configuring CDN over at docs.microsoft.com