Home › Forums › Classic DFFS › Trigger Rule with Autocomplete Field
- This topic has 15 replies, 2 voices, and was last updated 8 years, 1 month ago by Alexander Bautz.
-
AuthorPosts
-
-
October 11, 2016 at 15:19 #13597
-
October 11, 2016 at 19:12 #13600
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.
-
October 12, 2016 at 22:54 #13615
Thanks for the feedback – I have fixed this issue and will be posting a new version tomorrow.
Best regards,
Alexander -
October 13, 2016 at 03:31 #13617
As usual you are awesome!
-
October 13, 2016 at 22:22 #13630
Hi,
Could you check out v1.4.8 and see if the issue has been fixed?Best regards,
Alexander -
October 14, 2016 at 05:18 #13636
It 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)- This reply was modified 8 years, 1 month ago by DCH.
-
October 14, 2016 at 06:12 #13639
Hi,
Ensure the latest version has loaded correctly (that the old version is not casched) by hovering over the “Enhanced with DFFS” link, and clicking the “License and version information”. The “Autocomplete” version should read “1.4.8”.If it does not, try hitting “Ctrl + R” to force a reload.
Alexander
- This reply was modified 8 years, 1 month ago by Alexander Bautz. Reason: Mistakenly wrote about cascading dropdown plugin version
-
October 14, 2016 at 14:53 #13642
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.3 -
October 14, 2016 at 15:25 #13644
Ok 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). -
October 14, 2016 at 19:15 #13654
The correct version of the plugin must be loaded in the DFFS frontend. How does this “License and version information” look in the form?
Alexander
-
October 14, 2016 at 19:24 #13656
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.264 -
October 14, 2016 at 19:24 #13658
Just remembered that your DFFS version will not work with the latest AC plugin due to the method I user to call the “change” function.
Please update to the latest version.
I don’t think you need to use the new “installer” and “loader” functionality, just stick with the CEWP method if you have this already set up, but you need to change the “js” files to the latest version.
Alexander
-
October 14, 2016 at 19:31 #13661
Ok, I’m using the JSLink setup, but I’ll update the JS files now.
-
October 19, 2016 at 00:29 #13703
Ok, I updated everything to the latest. Here are my versions:
DFFS frontend: 4.4.1
DFFS frontend CSS: 4.19/4.14
Autocomplete 1.4.8
Cascading dropdowns 3.528
jQuery: 1.11.3
Lookup: not loaded
Resource management: not loaded
SPJS-Utility: 1.267
vLookup: frontend v2.276There doesn’t seem to be a change in the field behavior. What I am trying to do is make one field conditionally required depending on two specific values in the Autocomplete field.
-
October 19, 2016 at 00:50 #13705
I also noticed with the new 1.4.8 version of autocomplete, the confirmation light never turns green, just keeps spinning.
-
October 19, 2016 at 21:30 #13740
Could you email me a few screenshots so I can see exactly how you have set up the rules?
Also, please open the developer tools (hit F12 > Console) and see if you have any errors there when the spinner does not turn “green”.
Alexander
-
-
AuthorPosts
- You must be logged in to reply to this topic.