SharePoint upgraded to 2019 – will vLookup still work?

[BenR]

Alexander,

My firm has upgraded our SharePoint to 2019. I am running DFFS Classic, but having problems configuring a new vLookup configuration. Should I anticipate that DFFS Classic will work with SharePoint upgraded to 2019?

Version information

Custom DFFS-folder: DFFS_v4.4.5.49_2023-12-14
DFFS Loader: v2
DFFS frontend: 4.4.5.49 – September 30, 2023
DFFS frontend CSS: 4.65 / 4.65
Autocomplete: not loaded
Cascading dropdowns: 3.7.48 – September 22, 2021
jQuery: 3.6.3
Lookup: 1.1.20 – March 10, 2020
Resource management: 2.4.5 – August 29, 2019
SPJS-Utility: 1.356 – November 20, 2021
vLookup: not loaded

Licensed to

………. (Site collection license)

When I am configuring vLookup, the version is displayed: [vLookup plugin backend v2.2.165]

In advance, thank you for your support and efforts!

R’grds – Ben.

[Alexander Bautz]

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

[BenR]

Alexander,

Thank you for your response. It has been quite a while since I last used the Classic DFFS vLookup configuration – I may be rusty, but have used it before.

My issue is that in a NewForm or EditForm, the vLookup appears to be working partually… In the NewForm, the title of vLookup field (vLookupVersion) is inhibited (as set in vLookup configuration) – however the magnifying glass and add-new-child icons are not displayed. Additionally, an Attachement icon (paperclip) is displayed. Please see attached screenshot.

I’ve confirmed that the Attachment icon is added by DFFS by removing it from NewForm, icon disappeared, add DFFS back onto NewForm – icon appears.

As always, I appreciate your support and efforts!

R’grds – Ben.

Attachments:

1. 

   DFFS-vLookup-NewForm.png
   

[Alexander Bautz]

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,
Alexander

[BenR]

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.

Attachments:

1. 

   DFFS-vLookup-1.png
   

2. 

   DFFS-vLookup-2.png
   

3. 

   DFFS-vLookup-3.png
   

4. 

   DFFS-vLookup-4.png
   

[Alexander Bautz]

The 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

[BenR]

Alexander,

Yes, the Content Editor Web Part on the installer page is pointing the new SPJS installation I built from scratch – see attached.

Note that other DFFS functions are fine, just vLookup failing.

Really appreciate your insight!

R’grds – Ben.

Attachments:

1. 

   DFFS-vLookup-Installer_v2-Location.png
   

[Alexander Bautz]

Try 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

[BenR]

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 working

Switching 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 Bautz]

I 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

[BenR]

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?

Attachments:

1. DFFS-vLookup-New-Child-Error.txt

[Alexander Bautz]

Not 100% sure, but I think you might have a wrong field internal name in your setup for add new. Check both from and to in your setup and verify the field names are correct.

Alexander

[BenR]

Alexander,

Right you are! All working now in Google Chrome! When I hear back from my support organization about my Edge version, I’ll let you know what I find out.

In the meantime, thank you so much for your support, patience, and efforts for Classic DFFS!

R’grds – Ben.

[BenR]

Alexander,

I wanted to report back to you on an earlier issue – vLookup not working in Microsoft Edge Browser… I’ve heard back from my support organization and offer additional info

– Microsoft Edge Version 121.0.2277.112 (Official build) (64-bit).
– Our on-prem SharePoint Server 2019 – this SharePoint is in Edge-IE Mode (Enterprise Mode for Internet Explorer (or EMIE) a compatibility mode where Internet Explorer is required). This allows Edge to emulate IE11.

In Edge, when opening NewForm or EditForm (where vLookup is required), two errors reported in Developer Tool Console:
– SCRIPT1002: Syntax error, SPJS-ac.js (10,1)
– SCRIPT1002: Syntax error, SPJS-vLookup_frontend.js (9,1)

From NewForm or EditForm, open DFFS configuration, one error reported:
– SCRIPT1002: Syntax error, SPJS-ac.js (10,1)

From DFFS configuration page, select [Autocomplete] button, displays:
– The SPJS-Autocomplete plugin is not loaded.

Does this information identify how to troubleshoot where vLookup in Edge is needed?

Thank you so much for your support and efforts!

R’grds – Ben.

[Alexander Bautz]

Hi,
Yes, that helps. I’ll have to look into it, but think this should be fixable (I have enabled IE mode in Edge and get the same error).

Alexander

[Alexander Bautz]

I have published a new version – let me know if it fixes the problem.

Alexander

[BenR]

Alexander,

Thank you! I can confirm that errors regarding vLookup and Autocomplete are both resolved. In Edge browser (in EMIE mode), vLookup resolves, allows adding a new child record, and in DFFS configuration, there is no error for Autocomplete.

Thank you SO much for supporting Classic DFFS! You certainly keep your audience happy!

Sincere regards, Ben.

[Alexander Bautz]

Thanks for the feedback – I’m glad it worked.

Alexander

[Author]

Posts