› Forums › vLooup for SharePoint › Possible bug with DFFS_Loader.html 21st January 2018 release › Reply To: Possible bug with DFFS_Loader.html 21st January 2018 release
It seems I created a red herring in my initial assessment of this issue, I think there were some browser cache settings interfering.
The issue for us actually seems to lie in SPJS-vLookup_frontend.js.
I can install the very latest package of DFFS in it’s entirety and vlookup fails as per the original screenshot. If I then replace /SPJS/DFFS/plugins/SPJS-vLookup_frontend.js with the version from the 2017-12-20 package, vlookup fields immediately start to work correctly again.
Running firefox developer tools > network tab on an identical form, I get the following results consistently;
2017-12-20 vLookup_frontend: 73 requests, 4,045.71kB, 8.01s
2018-01-21 vLookup_frontend: 67 requests, 4,029.43kB, 7.52s
The 6 requests difference are the ones shown in the screenshot attached (using vlookup_frontend 2017-12-20), but with the later vlookup_frontend, they just don’t appear to fire at all.
Clicking the vLookup refresh button using vLookup_frontend 2017-12-20 returns the last 4 rows from the screenshot.
Is anyone else successfully running SharePoint 2010 and a vlookup version after 20th December 2017?