Forum Replies Created
-
Posts
-
SharePoint will do the heavy lifting easily for you using calculated columns. However, since calculated columns are not calculated until you save the item, and since they are not in the field dropdown picker on a DFFS form (if I’m wrong on either of those two points, someone please correct me) one possible solution is to NOT use DFFS.
You could build a simple SharePoint list with a single date field (make sure the Title field is not required), build a calculated date field for each due by date, and build a Datasheet (aka Quick Edit) view of the list where the user simply enters their Deploy Date, then clicks on the empty line below, and the calculated dates will all appear as soon as the record is saved.
In order to not clutter the list (since the records do not need to be saved long term) you could build a SharePoint Designer workflow that starts as soon as an item is created, pauses for 10 minutes (or 10 hours or 10 days – whatever interval you want) and then deletes the item from the list.
In order that the view is always blank when someone comes to it, filter the view to only show items where Created is equal to [today] + 1.
That approach may not meet your needs, but I thought I would suggest it as a possible simple solution in case it DOES meet your needs.
DFFS is amazing, but even native SharePoint can do ‘magical’ things when we apply a little creativity.
(Side note: if this turns out to be the exact solution you need, don’t fault yourself for not thinking of it earlier. I too spent several hours trying to develop a tool once using DFFS, and finally realized that a simple Quick Edit view would do everything I needed simply and elegantly.)
Good luck!!
William Summers recently had a project where he needed to put several dozen fields on a DFFS tab, and his users wanted a horizontal rule after every field. The following two suggestions came out of that experience.
SUGGESTION 1: Add space at bottom of the tab configuration pane so multiple fields can be added at once without having to scroll after each field is added. (William was able to accomplish this by adding the following at the end of the DFFS_backend.css file:
div.sectionWrapInner
{
padding-bottom:150px !important;
}SUGGESTION 2: Make it possible to copy and paste a single Header, HTML section, or table row, either to paste it into the same tab, or into another tab.
Paul, in case others are having a similar issue, in DFFS v 4.4.5.0, Alex made the following change:
“Added a new setting in the Misc tab to force attachments to open in a new tab.”I love that you figured out the code to make this happen yourself, and shared it with the community. It will undoubtedly come in handy for those using an earlier version of DFFS than 4.4.5.0 and who wish to remain on their older version.
Alex; I didn’t respond earlier because the site owner elected to simply change the titles of the offending items, so no follow-up was needed. I have another site owner using a different version of DFFS (4.4.4.22, released 2020-02-02) experiencing the same problem. The DFFS display form will not render for items with an apostrophe in the title.
When I examine the Console after loading the page, I’m seeing a number of errors. Whether they are caused by DFFS or by something else running in our environment I do not yet know. The two likely culprits are
1. a function called “SafeRunFunction” that is undefined (the apostrophe breaks an js statement inside a function called BuildBreadCrumb – probably not yours)
2. _spPageContextInfo is undefined inside a javascript function immediately following<!– DFFS CEWP Loader – February 02, 2020 –>
.
I’m attaching a screenshot of the Console errors, and of the code referenced by the second error.
In this case, there are currently 22 items on the list with apostrophes in their titles, and it appears it may be an ongoing challenge since titles contain words like “Don’t”, “Wasn’t”, etc.
If the underlying problem is a bug in SharePoint, not your code, we could perhaps create a workflow that removes any apostrophes from titles on list items.
One other thing I noticed when testing: If I tried to enter the backend from the “Direct To Backend” link on the installer page, I saw my DFFS Installer page (without displaying the installer web part) for a couple of seconds before the overlay displayed.
I did a quick test on another site and the radio buttons worked without a problem using version 4.4.4.22. I was helping Karen Flaxer, so am not able to test it again in her site right now, but its good to know that it is working. If I get a chance, I will try to see if I can recreate the issue in her site and report as much information as I can to you.
I’ll call your original list A and your new list B, and I’ll use the new form (newform.aspx) by way of example. Make sure you have applied DFFS to the newform on list B. Open the DFFS config for the newform on both lists, A and B. On list A, open the configuration page called “Import, Export and Restore”. Choose the Export button. Copy the code that is shown, then on list B, open the Import, Export and Restore configuration page, click the “Import” button, and paste in the code on your clipboard. Click the Save or Import button (I don’t remember exactly what the button is called off the top of my head) and your configuration is now applied to the newform of List A. Make sure to save the configuration. Rinse and repeat for each form on which you are using DFFS.
If I recall correctly, in version 4.4.4.0, there are colors entered in the Form background color setting in the Misc tab by default when a new config is created. I actually like having the default colors there, but having readonly fields adopt the same background color as is set in the Form background color setting makes the form look much nicer than having the readonly fields end up with white backgrounds while the editable fields have shaded or colored backgrounds.
Please have readonly fields adopt the same background color as formfields, eg:
.dffs-readonly-inner{
background-color:#e3e0e0;
}2 New Requests:
1. I often get requests to change the wording of the Save button to “Submit”. Can that be added as an option on the Tab configuration page?
2. I also get requests to hide the Cancel button. Can that be added as an option on the Tab configuration page?Suggestion: Add one more instruction in the tooltip for the “Set Field Value” setting in a rule.
I keep forgetting how to enter the current user’s email address (NOT a mail-to link) in a people field using the Set Field Value setting in a rule.
It’s a bit confusing:1. {currentUserEmail} will insert a mail-to link. 2. {currentUser:EMail} will insert the actual email address, which is VERY helpful when trying to populate a people field.
In the next release, could you add a note in the tooltip about using {currentUser:Email} to insert the user’s email address?
Adding Delete Button to vLookup table
https://spjsblog.com/forums/topic/delete-button-on-vlookup-table/#post-25523
