Forum Replies Created
-
AuthorPosts
-
Alexander BautzKeymaster
This is possible using custom js (advanced) – see this post for example code: https://spjsblog.com/forums/topic/vlookup-inline-editing-example/
Alexander
Alexander BautzKeymasterI haven’t heard about loading problems with vLookup in Edge before. I tested now with Microsoft Edge Version 122.0.2365.92 (Official build) (64-bit) and vLookup loads with no problems so I’m not sure what could cause this issue.
Did you see any errors in the developer console in Edge?
If you are able to set up a web meeting I can have a look at it to try to figure out what the problem is.
Alexander
Alexander BautzKeymasterTry bringing up the developer tools (hit F12) and select “Console”. Now try to reload the form and look for error messages in the console.
If there are none, please open the DFFS installer and click the “Update loader file” button at the bottom of the “Modify loader file” tab.
Any change?
If not, open the file /SPJS/DFFS/loader/DFFS_Loader_v2.html in a text editor and verify that it has a link to the file SPJS-vLookup_frontene.js
Alexander
Alexander BautzKeymasterThe attachment icon is automatically added on the attachment column by DFFS.
I’m wondering if your DFFS installer page links to an old installer file. Ensure your Content Editor Web part in the installer page points to this file:
/SPJS/DFFS/installer/DFFS_Installer_v2.html
Alexander
Alexander BautzKeymasterHi,
Yes, this should be an easy fix. You must open the list settings on your document library and index the field you use in your vLookup filter query (_vLookupParentIDif you followed the setup example). When this is done, your vLookup should be back in working order.Please let me know if you have any further questions.
Best regards,
AlexanderAlexander BautzKeymasterHi,
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,
AlexanderAlexander BautzKeymasterThe 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
Alexander BautzKeymasterHi,
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
March 19, 2024 at 17:38 in reply to: vLookup Callback Functions with Multiple vLookup Columns #37550Alexander BautzKeymasterThe callback from “vlookupChildAddedCallback” does not have any information about the form it return from, but you can use “vlookupAddChildPreCheck” to keep track of it – like this:
var current_vLookup_fin = ""; function vlookupAddChildPreCheck(fin){ current_vLookup_fin = fin; return true; } function vlookupChildAddedCallback(){ if(current_vLookup_fin === "vLookupTasks"){ // The fin is vLookupTasks - do shomething } }
Alexander
Alexander BautzKeymasterHi,
I’m not able to recreate this issue. Can you give me some more details?I did fix a similar bug in v1.0.41.0 – are you sure this site has the latest version?
Alexander
Alexander BautzKeymasterThanks for the feedback – I’m glad you got it fixed.
Alexander
Alexander BautzKeymasterThe “This field has been deleted or is not in the current content type” message most likely means that the field is not in the content type you are currently using.
Go to List Settings > Advanced Settings and ensure Allow management of content types is set to “Yes” (if it is No you must turn it on temporarily, but can change it back to No again after this procedure is done).
Now you can go back to list settings and under “Content types” click on the content type you want to address (most likely “Item”).
If the Title field is not shown you can click the “Add from existing site or list columns” at the bottom of the list of fields and under “List columns” find the Title field and add it to the content type.
When this is done you can turn off handling of content types again if it was initially set to “No”.
Alexander
Alexander BautzKeymasterThe license information is validated by reading the license file from my AZURE tenant. Does the user not have internet access on the computer where the form is used?
If they have, it might be a temporary network / AZURE issue that resolves itself. If they do not have internet access you can contact me to get a license code that is validated without having to read the license information from AZURE.
If they can see the DFFS configured form they have the necessary rights to the SPJS document library.
The error does not prevent saving the form data.
Let me know if you have any further questions.
Best regards,
AlexanderAlexander BautzKeymasterHi,
You must pass an unique value from the “parent” to the “child” when creating the new item, and then use this value to filter the records to only show the items created from this “parent”.See this setup example: https://spjsblog.com/vlookup-for-sharepoint/vlookup-setup-example-for-sp-2010-and-2013/
Alexander
Alexander BautzKeymasterHi,
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,
Alexander -
AuthorPosts