Forum Replies Created
-
Posts
-
Ok the hover over says:
Autocomplete 1.4.8
Cascading dropdowns 3.527
DFFS frontend: 4.365
DFFS frontend CSS: 4.14/4.14
jQuery: 1.11.3
Lookup: not loaded
Resource management: not loaded
SPJS-Utility: 1.267
vLookup: frontend v2.264Ok so a few more observations:
– I get that error in the console even when the rules works
– The only way to make it work consistently is when the user enters the value that should trigger the rule, removes focus from the field (click or tab away), adds focus back to the field (click or tab in), and removes it again (click or tab away).Ok here’s what I have loading:
DFFS Backend v4.365
CSS version: 4.11
spjs-utility version: 1.267
[SPJS-Autoccomplete plugin 1.4.8]
[vLookup plugin backend v2.261]
[Cascading dropdowns plugin v3.53]
jQuery 1.11.3It doesn’t appear to have made a difference. What are the minimum versions of all the other pieces you would recommend for this to work? I’m not on the absolute latest version of DFFS with the loader.
Also I found this error in the console:
TypeError: spjs.dffs.ruleObj.triggerMapContext is undefined
if(spjs.dffs.ruleObj.triggerMapContext[fin] !== undefined){
SPJS-ac.js (line 693, col 1)Ok it appears to be working, but with issues. It intermittently works and is effected by how the user leaves the field; whether they tab out or click the value in the autocomplete choices list. And it doesn’t seem to work on subsequent field changes after the initial value it set.
Cool thanks.
So my chart configuration is this:
Index 0 – SLT field – Split (also tried String)
Index 1 – Number field – Sum
Index 2 – Number field – Sum
Group by first column – True
Aggregation function – Count (also tried Sum)And with that I am now getting this error:
Error: Invalid type, Sum, for column “MyNumberColumn”
I noticed I am loading jQuery 1.11.3 on my master page but you included 1.12.3. Is that version required?
Oh, I should have mentioned this in my last reply. This has nothing to do with your scripts.
I didn’t know that at first because I encountered it while trying to setup DFFS, but its an IE11/SharePoint compatibility issue widely reported online. There is apparently no solution from Microsoft, but some work arounds have been posted by users.
Thanks!
Ok, after several days of undisciplined trial and error, the following combination seems to work:
– SP 2013 seattle.master
– IE11
– HTML5 doctype: <!DOCTYPE html>
– IE10 meta tag: <meta http-equiv=”X-UA-Compatible” content=”IE=10″/>
– This script in my master page: http://stackoverflow.com/questions/18829292/object-doesnt-support-this-property-or-method-error-in-ie11Thanks!
Just an update… I had changed the DOCTYPE declaration in my seattle master page to a simple HTML5 one, but when I changed it back to the default, it still failed in IE11 but worked in IE10 emulation, Chrome and Firefox.
