[AdamP]

Hi Amal

Personally I’d suggest trying a completely new install of DFFS on a new subsite, keeping it as minimal as possible, just a basic list and form to start with.
Once you’ve proven that there are no issues, progressively add more configuration until the problem arises.

Adam

[AdamP]

Hi Nicole

If I understand your situation correctly, Alexander has already thought of this and included it as standard;
-In DFFS config there is a check box for “Autofill subsequent dropdowns when they contain only one valid option”
-Standalone there is a parameter to set – “autoselectSingleOption:true If the next dropdown contains only one option it will be automatically selected.”

Have you tried either of these?

See guide

Adam

[AdamP]

Possibly not the answer you’re looking for, but a quick workaround in the short term may be to get (or request) the list view threshold increased – the default OOTB threshold is 5000 items, but that’s a threshold, not a hard boundary
SharePoint software boundaries and limits
We have increased ours to 50,000 items without any performance issues.

As for querying the child list itself – this post might be of use; StackExchange

[AdamP]

Hi Amal
Is there any reason you can’t either;
-give users read access to the root of the site collection
-Set up DFFS directly on the Products sub-site

If you can’t do either of those then on the root site you’ll need to try granting at least some access to all users so they can use services – I’d suggest a minimium of “Use Remote Interfaces – Use SOAP, Web DAV, the Client Object Model or SharePoint Designer interfaces to access the Web site.” That might work, but you may run into other errors (I’ve not tried this scenario myself).

Adam

[AdamP]

Hi Alexander
-SP2010
-We were primarily using “Rich Text” but “Enhanced Rich Text” also seems to be affected in the same way (appears as a plain text box without the edit icons above)
-DFFS frontend: 4.4.1
DFFS frontend CSS: 4.19/4.19
Autocomplete: 1.4.7
Cascading dropdowns: 3.528
jQuery: 1.12.4
Lookup: 1.1.5
RM: not loaded
SPJS-Utility: 1.267
vLookup: frontend v2.2.76

It’s just strange that from a parent dispform the issue doesn’t occur – it’s only when the parent is editable that the child form “opens” incorrectly.

[AdamP]

Thanks Alexander

Much weirdness going on here, but I think we’re making some progress.

I do have access to change compatibility view settings, but others here won’t, and it looks like changes there don’t have much, if any, effect.

I have had some success with playing tunes on the emulation tab though. While doing that I’ve realised that the Rich Text Editor control only seems to display correctly in the default modes (doc mode 8, user agent IE11) – and anything entered into the rich text editor just isn’t recognised at all. The result of

spjs.utility.getFieldValue({"fin":"Consultee"}).replace(/<[^>]*>|\s| |xA0;|\u200b/g,'');

is simply

""

If I change the emulation mode to anything other than the default, the Rich Text Field is rendered as a simple text box (text within is then recognised and the form can be saved – everything normal, except for the fact that it’s not a rich text field anymore).
See attached screenshots.

I’ll try some more tests on the build that functions correctly tomorrow to compare with the tests above, but I’ve got a feeling that something just isn’t quite right with this laptop build, unless you can think of a reason that the content of the RTE control would be completely inaccessible?
I did find these two posts by Marc Anderson
http://sympmarc.com/2011/02/10/finding-the-contents-of-a-sharepoint-rich-text-column-with-jquery/
http://sympmarc.com/2011/02/14/finding-the-contents-of-a-sharepoint-rich-text-column-with-jquery-and-changing-it/
Using `$(“textarea[Title=’Who have you consulted prior to this challenge’]”).closest(“span”).find(“iframe[Title=’Rich Text Editor’]”).blur(function(){
alert($(this).contents().find(“body”).html());
});` I’m able to alert the html contained within the RTE field – see third screenshot

That code is quite similar to getFieldValue_SPFieldNote_HTML in spjs-utility.

	"getFieldValue_SPFieldNote_HTML":function(a){
		var f = spjs.$(spjs.utility.data.fields[a.fin]), v = "";
		if(browseris.ie5up && browseris.win32 && !IsAccessibilityFeatureEnabled()){
			if(f.find("iframe[class^='ms-rtelong']").contents().find('body').html() !== ""){
				v = f.find("iframe[class^='ms-rtelong']").contents().find('body').html();
			}else{
				v = f.find('textarea:first').val();
			}
		}else{
			v = f.find('textarea:first').val();
		}
		return v;
	},

browseris.win32 caught my attention – Will getFieldValue fail to target the correct values if I’m running in 64bit IE11? browseris.win32 in the console returns “false”… browseris.win64bit = “true” !

I’ll try to get into IE 32bit mode somehow and report back.

Adam

Attachments:

1. 

   DFFS-DM8-UAIE11default.png
   

2. 

   DFFS-DM8-UAIE10.png
   

3. 

   DFFS-RTE-contents.png
   

[AdamP]

For me, both are running in compatibility view…
…”/Lists/Challenges/NewForm.aspx?RootFolder= is running in Compatibility View because ‘Display intranet sites in Compatibility View’ is checked.” Document mode for both is 8 (default) “via X-UA-compatible meta tag” (it’s a SP2010 site), and user agent is “default” for the functional version, and “Internet Explorer 11 (Default) for the non functional one.

I’m starting to think it’s related to the specific build of the laptop and IE version in use. Things seem to get worse with Developer Tools open – the “Add-on failed to run” pop up and lots of errors if I run network analysis – 500 on lists.asmx, and various 401’s, 404’s and 407’s, and important things like jquery “pending”.

[AdamP]

Hi Alexander

Problematic- IE version: 11.306.10586.0 Update versions: 11.0.31
Normal- IE version: 11.0.9600.18500CO Update versions: 11.0.36

All multiline text fields where “required” has been set by a DFFS rule seem to be failing (here and on other forms)

The fields themselves look completely normal. I did a text difference comparison on the page source html – completely identical except for a value for id=”__REQUESTDIGEST” which would appear to be some sort of internal form validation.

Adam

[AdamP]

On the problematic machine I get an empty value for console.log(test); both when the form loads and the fields are empty, and after trying to save with values in the fields. Other fields correctly return the value entered in the field (and typeof=string)

undefined

string

On the machine without the issue, doing the same test on the empty form returns;

undefined
<DIV></DIV>
string

(Also the same if I leave the field empty and try to save).

Is there anything else that would be useful to look at?

[AdamP]

I’m seeing the same error, but on multiline text fields (rich text), I haven’t yet tried on a people picker.
The fields are populated, but on save they all show in red text “You must specify a value for this required field”.
Oddly – this only occurs on a laptop with a different build to my desktop machine (both IE 11, but slightly different versions). I’m also getting frequent popups stating “An add-on for this website failed to run” – as yet I can’t determine what isn’t running.

DFFS Frontend 4.4.1
DFFS Frontend CSS 4.19/4.19
Autocomplete 1.4.7
Cascading Dropdowns 3.528
jQuery 1.12.4
Lookup 1.1.5
Resource Management not loaded
SPJS-Utility 1.267
vLookup frontend v2.2.76

Anything to look for to track down the problem?

Adam

[AdamP]

Some of these are in the installation guide with descriptions;
https://spjsblog.com/commentbox-for-sharepoint/installation-manual/ under the section for ‘configuration options’

The group/ID is the underlying sharepoint ID number from the user information list. Multiple can be added separated with commas.

For text area expanded by default – try the ‘textareaVisible’ option

Author to delete is a question for Alexander, but I can’t see how that would easily be achieved – if a parent comment is deleted then child comments would have no item to hang off. Personally I would stick to the default behaviour – authors can edit to remove all text, but any follow up replies would remain unaffected.
I’ve not used commentbox-for-sharepoint for a while, but I think it’s also advisable to enable versioning on the list when enabling authorCanEdit so that any posted/removed comments can be audited (depending on your usage case).

Adam

[AdamP]

I think I’ve seen this recently too – SP2010, and using one of the latest releases of DFFS. The overlay looked similar to the one in the screenshot – not quite fitting the underlying form.
I didn’t have time to investigate at the time so I reverted back to a known good version I was using on a different site.
The DFFS overlay that is working for me is; Version: December 14, 2015
I believe the one I had trouble with is;Version: May 12, 2016 – They appear to be slightly different (both being used with their corresponding versions of DFFS etc)

Old;

<style type=”text/css”>
table.ms-formtable{
visibility:hidden;
}

New;

<style type=”text/css”>
table.ms-formtable{
position:relative;
left:-10000px;
}

[AdamP]

They’re just standard SharePoint lists – enable versioning as usual through list settings > versioning. DFFS just stores it’s data there.

[AdamP]

I always enable version history on my SPJS configuration lists – I’ve never needed to use it, but I think that would allow roll-back of specific configurations (just be careful of column additions/deletions)

[AdamP]

Thank you Alexander! This does the job perfectly.

I did initially think it hadn’t worked as I had left the ajax options enabled from the last test – in that case none of the vLookup data will display. Disabling them all (back to defaults) made everything work. Something to remember to check if people are having problems.

Adam

[Author]

Posts