-
Search Results
-
In reply to: Custom Scripts
From what I have seen this will not affect Content Editor Web Parts that have already been added to a page.
This means that lists where DFFS has already been installed will not be affected, but installing DFFS to a new list will require that “scripting” is turned on in the site using the admin-center or PowerShell.
This setting will most likely be automatically reverted within 24 hours so in that case DFFS must then be installed on the new list in that 24-hour window.
Updating DFFS for lists that are already installed is not affected as this doesn’t require any modifications on the Content Editor Web Parts in the list forms.
This is the link to Microsoft’s article describing how to enable custom scripting: https://learn.microsoft.com/en-us/sharepoint/allow-or-prevent-custom-script
PS: The new modern DFFS version for SharePoint online is not affected – only the Classic version of DFFS.
Alexander
In reply to: Vlookup filter not working
Hey Alexander, I didn’t want to create a new post for this, but I am also seeing an issue with the filter for vLookup.
Here’s my setup:
– Parent list with a column labeled _DFFSID
– Child list with a column labeled _vLookupProjectID
(this is also the FIN for both columns, I have verified that)
– In my parent list I am configuring the vLookup with the “select web” button to get the website and then selecting the child list in the dropdown.
– In the filter I have the following: _vLookupProjectID eq ‘[[fieldValue:_DFFSID]]’
– I save the editor and go to the actual form and it’s telling me “Column ‘_vLookupProjectID’ does not exist. It may have been deleted by another user.”
– Note that in the “build the table” and “add new item” tabs I am able to select _vLookupProjectID in dropdowns to build the table and prefill the form, so it’s a valid column
– If I change the filter to use Title instead of _vLookupProjectID then it works perfectly fine. I don’t get it.My hypothesis is that it’s related to the leading underscore being the problem. My theory lies in the fact that I created a different column that didn’t lead with the underscore, but the rest was the exact same. So it was vLookupProjectID and that one worked as well.
I have the latest version of modern DFFS installed. Take a look and tell me what you think.
I have modern DFFS installed in my site collection app catalog, but I don’t use it on all of my lists. I’ve noticed that on lists where I have a lookup column, if I click on the hyperlinked value in the lookup column it will try to open it in modal with modern DFFS, but if I don’t have a form created for that parent list in modern DFFS I get a “No configuration found” error.
Is this expected behavior that modern DFFS will always try to open the modal window of a lookup column even if modern DFFS isn’t used in that list? Any way around it?
In reply to: Easy way to make all fields readonly?
You basically just remove the contents of the /SPJS/DFFS folder and upload the contents of the zip-file you downloaded.
If your old installation was done using the “version 1 installer” you should update to V2 and then use the installer to uninstall and then reinstall DFFS to the forms.
The uninstall / reinstall will not affect your configurations – they are stored in a separate list in your site and will pop back when you reinstall.
Follow the instructions in the installation manual here: https://spjsblog.com/dffs/dffs-installation-manual/#Upgrading_from_a_previous_version
Alexander
I think this might be related to a field that has been deleted from the list, but it is used in for example a rule in the form.
I have made some changes earlier to try to catch this kind of errors, but I might have missed something.
Do you know if a field has been deleted recently? – if so, do you know where in the config it was used?
You can open the configuration list (/Lists/DFFSConfigurationList/AllItems.aspx) and manually edit the configuration blob to remove that field, or you can delete the config for that form to start over.
Alexander
In reply to: Timing issue: Autocomplete vs. Cascade
This is hard to replicate without having the exact same setup in the list.
Did it stop working when you updated to a new DFFS version?
I’m not sure exactly how you use the AC and the CASC in the form, but if you always start with the AC you should wait to initialize the CASC until the AC has completed filling the fields – then the CASC should populate correctly when initialized.
Alexander
Alexander,
I have opened a ticket with my support organization and will let you know what I find out.
In Chrome, when I add a new item to the Parent list, I see the vLookupID field populated (works!). From the NewForm in the Parent list, I click to add a new item (to child), a dialog box opens and displays the whirly-gig and eventually resolves to “This took forever!” Developer Console reports the error in the attached file.
What can we do to troubleshoot?
Alexander,
Found an issue – vLookup is sensitive to the browser! My firm provides three browsers, Chrome, FireFox, and Edge. Recently, I’ve switched to Edge because of two features in SharePoint that it does, but Chrome and FireFox do not (Data View Properties – XSL or Parameters Editors, and multi-line paste to Data Sheet View).
Browsers:
Edge – Version 121.0.2277.112 – vLookup not loading
Chrome – Version 120.0.6099.217 – vLookup working
FireFox – Version 115.3.1esr – vLookup workingSwitching to Chrome (I will advise users on the landing page to use Chrome to work on this site…).
Now that things are displaying on all forms correctly, I have a remaining problem…
When I add a new item to the Parent list, I see the vLookupID field populated (works!). From the NewForm in the Parent list, I click to add a new item (to child), a dialog box opens and displays the whirly-gig and eventually resolves to “This took forever!”
If I manually create the child record, copying the parent vLookupID, it will display correctly in the parent. So, the problem is with creating a new child record (from either parent NewForm or EditForm – I have created the _vlookupID and _vlookupParentID).
Do you have advise how to troubleshoot this create child record issue?
I am overwhelmed that you are helping me with Classic DFFS!
R’grds – Ben.
Alexander,
Following your instructions, I have rebuilt from scratch.
1) New download of latest Classic DFFS, new Installer_v2
2) Create new SP Subsite, create new Lists – see DFFS vLookup 1.png
3) Installer_v2 to new Parent list – see DFFS vLookup 2.png – note that the Attachments icon is displayed simply by adding DFFS to the NewForm.
3) Turn off attachments for the list – see DFFS vLookup 3.png – note that the Attachments icon displays below the fields, but not on the Ribbon.
4) Configure DFFS for NewForm, configure vLookup for NewForm- see DFFS vLookup 2.png – note that the Attachments no longer displayed,
Title of vLookupVersions field not displayed,
Magnifier Glass not displayed,
Add new child (+) not displayed,
The version information still says that vLookup is no loaded.Does this help troubleshooting?
R’grds – Ben.
Hi,
I think you need to uninstall and reinstall your Classic DFFS using the v2 installer. I’m wondering if you might have updated DFFS partially and not replaced the entire package?Please set up the v2 installer as described in the installation instructions and uninstall / reinstall. The form configuration is not affected by this uninstall / reinstall as the configuration is stored in a list in the SharePoint site and not in the DFFS web part itself.
Regarding the attachment icon: This does not have anything to do with vLookup, but is added on the attachment field itself. If you don’t want to show the attachment field in you form, either disable attachments in the list settings, or use tabs to configure a form using only a subset of the fields available in the list.
Let me know if you have any questions.
Best regards,
AlexanderIn reply to: Max vLookUps
The only thing that limits it is that a large number of queries to fetch the data from the different lists will take some time to load. I recommend splitting the vLookups in different tabs (they are only loaded when they are visible) to ensure the form does not take to long to load initially.
Alexander
Hi,
Yes, vLookup will still work in the forms, but if you use the “modern list views” displaying the vLookup field in the list view will not work.What kind of problem are you experiencing?
Alexander
Hello,
I had a user test a form for me and they had this banner across the top of their form: “Error loading the DFFS license file. If you are the owner of this site you must contact SPJSBlog to resolve this issue (attached).
Their permissions are list-based only and the lists sit at the parent level. Is this error displaying because they do not have access to the ‘SPJS’ folder where the configuration is?
Additionally, will this error prevent the user from saving the form?
Thank you
Attachments:
In reply to: Export Settings From DFFS V4.4.1
Hi,
v4.4.1 is from 2016 so you won’t have the latest version features.You might be able to upgrade to the lates version, but I cannot guarantee that this will work when you upgrade from a 8 year old version.
To do a proper upgrade, you must delete the DFFS folder in your SPJS document library and upload the new version of DFFS.
This will not affect your configurations as these are stored in a separate list.
When you have uploaded the new DFFS version and configured the DFFS installer you must uninstall and reinstall DFFS in the forms for your list.
If this works you are good to go, if not you must downgrade the DFFS version and try to do a step by step upgrade a few versions at the time (you must open the config and save it in each version to ensure you apply the features from this version) – not sure how this will work out as you have such an old version…
Let me know if you have any questions.
Best regards,
AlexanderIn reply to: vLookup Document upload form
