This is a strange compatibility issue so have a ticket open with Microsoft so will update with the real fix (i'm assuming that it will be a hot fix).
When you open a people picker in IE 11 for a infopath form in the browser, the error get's thrown, JSON is undefined.
the temporary fix is to add teh following to the pickerdialog.master in the layouts folder.
Add this to the top of the page:
<!DOCTYPE html>
Replace the meta tag where it has
<meta http-equiv="X-UA-Compatible" content="IE=10" />
with the following:
<meta http-equiv="X-UA-Compatible" content="IE=edge;chrome=1" />
<!--[if lt IE 9]>
<script src="http://code.jquery.com/jquery-1.10.2.js"></script>
<![endif]-->
<!--[if gte IE 9]><!-->
<script src="http://code.jquery.com/jquery-2.0.3.js"></script>
<!--<![endif]-->
Save.
Test your people picker on infopath browser form.
When you open a people picker in IE 11 for a infopath form in the browser, the error get's thrown, JSON is undefined.
the temporary fix is to add teh following to the pickerdialog.master in the layouts folder.
Add this to the top of the page:
<!DOCTYPE html>
Replace the meta tag where it has
<meta http-equiv="X-UA-Compatible" content="IE=10" />
with the following:
<meta http-equiv="X-UA-Compatible" content="IE=edge;chrome=1" />
<!--[if lt IE 9]>
<script src="http://code.jquery.com/jquery-1.10.2.js"></script>
<![endif]-->
<!--[if gte IE 9]><!-->
<script src="http://code.jquery.com/jquery-2.0.3.js"></script>
<!--<![endif]-->
Save.
Test your people picker on infopath browser form.
Did you get a response from Microsoft for your support ticket ?
ReplyDeleteWe're experiencing the exact same problem !
Yeah, they have acknowledged that it is a bug. Also the Infopath team and the IE team are working on a fix but no estimate on when the permanent fix will be available.
DeleteIs there any official solution at the moment? (Maybe in December CU) I couldn't find anything on the net.Thanks!
Deletethe ticket is still open and they are still working on it.
DeleteI am happy to report (just got the news last night), that microsoft has acknowledged the issue with the formserver.aspx page explicitly setting the document compatibility mode to IE8 and that there will be a fix out in the first or second SharePoint 2013 Cummulative Update (CU) in 2015.
ReplyDeleteWill update the post when they tell me which one.
Ok. April CU is when this fix is supposed to be release!
ReplyDeletehttp://support.microsoft.com/en-us/kb/2880473
ReplyDeleteWas browsing the March 2015 CU and found the above. I have sent a request for information to the PFE, if the fix was included in the March CU and not the upcoming April CU.
Ok. Got response from support engineer. She said that it was released in the March CU but there is additional testing pending for April. So i am waiting some fixes (workflow issues) that is supposed to be in the April 2015 CU so i will wait till it comes out since we are so close to the April CU release date (ok, the rumor is that there are some major issues with the upcoming CU, fingers crossed that it is just rumors and it is not true).
DeleteFixed with the March 2015 CU
ReplyDeleteI am experiencing the same problem and I have the March 2015 CU installed. What is your compatibility mode setting for your InfoPath forms? Mine is IE8.
ReplyDeleteX-UA-Compatible content="IE=11"
Deletecheck that the url is not in the compatibility View settings list but it should still work with the url in the list.