Forum Replies Created
-
Posts
-
Update: I FIGURED THIS OUT!
My company loads a version of jQuery automatically into our SharePoint sites. It’s 1.11.3, there’s nothing we can do about it.
I added a line of code in my SharePoint Master Page to load jquery 1.12.4, because I know that’s what you use for DFFS, and I have it at the bottom of the master.
Out of curiosity, I added console logs in the spjs-casc.js file to see which jQuery version it was recognizing on start. Sure enough, it was capturing the 1.11.3 version and not the 1.12.4 version when it is initially loaded. Bingo, problem found.
I moved the invocation of 1.12.4 to the <head> of the master page, after the default .js invocations, and I added Defer=”True”, and I removed where I had LoadAfterUI=”true”, I took that piece out altogether.
Now it’s working perfect!
My console errors dropped tremendously as well. I’m no longer getting the TypeError: a is undefined at all, but I was getting the XML Parsing Error 3 times all at once, now I’m only getting it 1 time.
So I still need to figure out why I’m getting even 1 instance of XML Parsing Error, but it’s better than 3, plus my cascading dropdowns are working perfectly again.
I tested the same console logs to make sure that the 1.12.4 version were capturing on load, and they are.
I’d like to follow up on this, as I have just noticed I am having the exact same issue, however I am only having this problem in FireFox. It’s working fine in Internet Explorer.
I’m not sure if this is truly indeed the root cause of the problem, but I noticed it when I have a cascading dropdown where the lookup column may have blank values.
If I move that column to the very top of the cascading dropdown, it doesn’t give me any choices to choose from at all.
The column in question is a people field.
I’m also getting XML Parsing Error: not well-formed errors, but I cannot click to see where exactly the error is in the code.
So as an example, I’ll have the following cascade setup:
Title,PeopleField/Title
Now the title field has values for all records, but only some records will have values in the associated PeopleField. Instead of showing me the choices of the PeopleField, it’s just not showing me anything at all, which I assume is because some values are blank.
It’s at this point in the process where in Firefox I get this error: TypeError: a is undefined
Again, this is not an issue in Internet Explorer.
DFFS v4.4.2.8
CCDD v3.6.9Hi Alexander, no worries!
I did find a bit of info in your change-log for SPJS-Lookup that describes exactly the functionality I’m hoping you can implement for cascading dropdowns, which is
addYouOwnValue
on: true or false. This controls whether or not to show a link to “kill” the dropdown and show the underlaying text field.
Just something to keep in mind, thanks for all you do!
Checking back in, I just installed the latest version of DFFS and this dropdown functionality works perfectly now! You are the MAN!!!
Thanks for looking into it Alex. Excited to see what you come up with. Don’t know what I’d do without this software.
Hi Alex,
Following up, and yes I am able to use a multilookup column, but I cannot use it anywhere in my configuration. I’m attaching a few screenshots to make sure I describe the issue (and my request) as best I can.
So I have a source list, we’ll call it Test1 (see image labeled Test1 for this). That has 3 columns:
TestColumn = Single Line of Text
Lookup1 = Lookup Column (allow multiple choices)
Lookup2 = Lookup Column (allow multiple choices)Then, I have a list called Test2 which has 3 columns that I’m using for Cascading Dropdowns, you can see the configuration in the image labeled CCDD:
Test1 = Single Line of Text
Test2 = Multiple lines Text
Test3 = Single line of TextYou’ll notice in the image labeled CCDD that my column labeled Test1 is assigned to the multichoice lookup column labeled Lookup1 in the source list.
Then, in image labeled Test2, you’ll see that the Test1 column works, I can select from the multichoice column, but the subsequent dropdowns do not work. Multichoice columns in the source list can only be used as the very last configuration.
So what I’m needing (and this is possible in SPServices Cascading Dropdowns, but overall yours are better), but what I need is to be able to have the multichoice column that I’m looking to in the source list be able to work anywhere in the configuration, not just the last step.
Am I making sense? So basically, in image Test1, I want the column called Lookup1 to be able to be in the middle of my configuration and all the dropdowns still work.
Attachments:
