Hi Marc, All;
We've been using the Cascading drop-downs in SP2010 for some time. The parent/child columns are primarily of type 'lookup', although some are 'choice' columns. This worked perfectly in SP2010.
We've recently upgraded to SP2013. They still worked perfectly in SP2013 before doing the visual upgrade. After doing the visual upgrade, we found that most of the cascading drop-downs were broken. After much troubleshooting I have found the cause but not a fix.
The cascading dropdowns where the column is of type 'lookup' work in IE8, IE11, and Chrome. They do not work in IE9, IE10, or IE11 with compatibility mode on. The reason is that in IE9 and IE10 mode, the lookup fields are not just a simple drop-down, but they're actually fancier with the ability to type into the dropdown field for auto-completion. I don't understand why this only happens in IE9 and IE10 but that has been the experience. These "fancier" drop-down fields do not play nicely with the cascading drop-downs. I have tried several releases of SPServices and JQuery, including the latest.
The behavior I've observed is that the "fancier" lookup fields require a double-click to select an item, and that selection event does not appear to be picked up by the child column as it acts like there has been no selection in the parent column.
The columns of type "choice" work fine in SP2010 and SP2013 and in any browser.
The issue does not appear to be related to 2010 upgrade as I have created new forms, etc.
What I would like is either A) tweak SPServices to work with the "fancier" lookup fields, or B) find out how to disable the "fancier" lookup fields on the page so that they're just a simple drop-down in IE9 and IE10 display modes.
Marc, I've chatted with you at SPTechCon before. Let me know if I should just shoot you an e-mail about this. I'm posting here as I couldn't find anything about this issue so thought it might be good public knowledge. I can't post a screenshot of our example publicly but could e-mail it to you.
Thanks,
Tommy
We've been using the Cascading drop-downs in SP2010 for some time. The parent/child columns are primarily of type 'lookup', although some are 'choice' columns. This worked perfectly in SP2010.
We've recently upgraded to SP2013. They still worked perfectly in SP2013 before doing the visual upgrade. After doing the visual upgrade, we found that most of the cascading drop-downs were broken. After much troubleshooting I have found the cause but not a fix.
The cascading dropdowns where the column is of type 'lookup' work in IE8, IE11, and Chrome. They do not work in IE9, IE10, or IE11 with compatibility mode on. The reason is that in IE9 and IE10 mode, the lookup fields are not just a simple drop-down, but they're actually fancier with the ability to type into the dropdown field for auto-completion. I don't understand why this only happens in IE9 and IE10 but that has been the experience. These "fancier" drop-down fields do not play nicely with the cascading drop-downs. I have tried several releases of SPServices and JQuery, including the latest.
The behavior I've observed is that the "fancier" lookup fields require a double-click to select an item, and that selection event does not appear to be picked up by the child column as it acts like there has been no selection in the parent column.
The columns of type "choice" work fine in SP2010 and SP2013 and in any browser.
The issue does not appear to be related to 2010 upgrade as I have created new forms, etc.
What I would like is either A) tweak SPServices to work with the "fancier" lookup fields, or B) find out how to disable the "fancier" lookup fields on the page so that they're just a simple drop-down in IE9 and IE10 display modes.
Marc, I've chatted with you at SPTechCon before. Let me know if I should just shoot you an e-mail about this. I'm posting here as I couldn't find anything about this issue so thought it might be good public knowledge. I can't post a screenshot of our example publicly but could e-mail it to you.
Thanks,
Tommy