Forum Replies Created
-
Posts
-
I have created a support ticket with Microsoft regarding this bug as it also happens when I build the “HellowWorld” example List View Command Set extension.
See my support ticket below for details (it seems to only occur in Google Chrome).
Best regards,
Alexander********************************************************************
Support ticket registered with Microsoft
********************************************************************
When deploying a ListView Command Set extension on SharePoint Online (/_vti_pvt/service.cnf vti_extenderversion:SR|16.0.0.24301), a list that has a lookup column to another list in the site throws a “Something went wrong” error like this if you reload a list view of the list:
Expected double-quoted property name in JSON at position 29738 (line 563 column 10162)This only happens in Google Chrome (currently tested in Version 119.0.6045.160 (Official Build) (64-bit)). It does not happen in Edge (Version 119.0.2151.58 (Official build) (64-bit)) or FireFox (119.0.1)
From what I have found, it is related to IndexedDB > ODSP_DB and it goes away after 10-15 minutes or if I clear the site data (F12 > Application > Storage > Clear site data).
The error can be reproduced by building the HellowWorld example from this site: https://learn.microsoft.com/en-us/sharepoint/dev/spfx/extensions/get-started/building-simple-cmdset-with-dialog-api
As mentioned, clearing the site data or waiting 10-15 minutes fixes the issue, but you can make it reappear by going to the app catalog, selecting the app and go to the “Deploy” button in the banner and redeploy it. Return to the list view of the list containing the lookup column and the error is back.
Please note that it only happens when the sppkg file is built and installed to either the tenant app catalog of a site collection app catalog and not when using “gulp serve”.
It is a caching issue in the browser that causes the error when you update the version.
Either wait 10-15 minutes for the indexedDB to auto-refresh, or hit F12 to bring up the developer tools, click the Application tab and then Strorage and click “Clear site data”. See attached image for details.
Alexander
Attachments:
It might be the jQuery version – maybe you have some custom js that does not play well with the latest version of jQuery.
Do you see any errors in the developer tools (F12 > Console)?
You can try just replacing the current jQuery file in the /plugins folder with the one from an older version to see if that is the issue.
Alexander
Hi,
The configuration for the forms that use the Modern DFFS is stored in a hidden list named DFFSConfigurationList in each site that you can find by typing in the list path like this: “/Lists/DFFSConfigurationList/AllItems.aspx”.You can use for example powershell to look for this list in all the sites and then loop over the items to list out the “Title” and the “Form” fields – it will show all the lists / forms that use the Modern DFFS in that site.
The method EJ mentioned will not work for the Modern DFFS because the form url override is not used by the Modern DFFS.
Alexander
The default length of the suggested items (the items shown without applying a filter) has been 25 since the beginning of the Modern DFFS (if I remember correctly), but I’ll add a setting in the field properties pane where you can set the suggested items length in the next version.
Alexander
If I understand correctly you want to style alternating rows – the jQuery code to do that is like this:
jQuery(".add_classname_here:odd").css("background-color","green");Alexander
Can you add a screenshot or two of what you have configured and how it looks in the form so I can look at it?
Alexander
Hi,
I’m not able to recreate this issue. Can you look at the developer tools (F12 > Console) when you load the form and click the edit button to see if you have any errors there?Also, in your Miscellaneous tab – have you toggled “Use TinyMCE as a rich-text editor in the forms to support tables and more options for formatting” on or off?
Alexander
There is no validation of the input in the popup dialog, but because the value is written to the form you can create a rule in your DFFS configuration to set the field as required – this will not allow saving the form if the field is empty.
Alexander
It looks like the file /SPJS/DFFS/css/DFFS_backend.css is not loaded.
I think this is related to a bug in SharePoint 2019 – read more here: https://blog.stefan-gossner.com/2018/11/30/common-issue-sp2019-items-in-document-libraries-are-downloaded-with-mime-type-application-octet-stream-rather-than-the-accurate-one/
Alexander
On second thought I already have a method to override it. Open the developer tools (F12 > Console) and type this in the console:
window["__modernDFFS_" + _spPageContextInfo.listUrl.split("/").pop()] = {"new": false, "disp": false, "edit": false};It should disable the Modern DFFS until you refresh the page.
Alexander
Not that I’m aware of. I’ll look at adding support for an URL search string parameter like “?disableDFFS=1” or something like that.
I guess the easiest method for you is to just remove the Modern DFFS solution from the APP catalog – do the changes and then add it back.
Alexander
