At first I figured this would be easy, but it turns out it is not.
I tried this first:
http://[server]/[site]/[list]/Forms/Template.xsn.
Perfect! Except that this does not work in FireFox. Turns out that even with a link directly to the file, SharePoint runs some javascript behind the scenes to see how the file should be displayed. It attempts to create an ActiveX Object, which fails in Firefox. The function is written poorly as when the ActiveX create fails, it attempts to open the form using Form Services.
Our form was not Form Services compatible so we were getting errors when Form Services tried to expose the form.
Long story short, it didn't work.
I began digging and found other posts that simply paste the JavaScript that SharePoint uses into a Content editor web part. Unfortunately that wasn't going to work for me as our client utilizes links lists and needed a way to expose them via a URL.
That didn't work either.
After digging around in the javascript files a little more I decided to take a new route.
I installed and monitored the network traffic with Fiddler. I found that SharePoint actually changes pages a few times before the forms are exposed. I tried the different links it was navigating to until one worked.
Here is the solution!
https://[server]/[site]/[list]/forms/template.xsn?OpenIn=PreferClient&NoRedirect=true&XsnLocation=/[site]/[List]/forms/template.xsn
Hope this saves someone else some headache!
No comments:
Post a Comment