General

Re: SharePoint 2013 and 2019 Form Library Edge

oOoSLIPPYoOo — Fri, 14 Feb 2020 16:28:43 GMT

Hi, Hilary! Thank you for your reply. Here are two link code examples that work in IE compatibility mode and Edge compatibility mode.

Example 1

<script language="vbscript">
' Set the URL to the form Library.
' Note that it must NOT be URL encoded (e.g. use " ", not "%20").
Dim urlLibraryPOR
Dim urlTemplatePOR
urlLibraryPOR = "http://WebApplicationTitle/sites/SiteCollectionTitle/FormLibraryName/"
urlTemplatePOR = urlLibraryPOR + "/Forms/template.xsn"

Sub CreateNewInfoPathPOR
   Dim objOpenXMLDocuments
   Set objOpenXMLDocuments = CreateObject("SharePoint.OpenXMLDocuments")
   objOpenXMLDocuments.CreateNewDocument2 window, urlTemplatePOR, urlLibraryPOR
  End Sub
</script>
<center>
<table><tr><td><center>

  <button style="background-color: #E5E9F4" onclick="CreateNewInfoPathPOR()">
   <font color="#1F3E6D">
    <B>Submit Button</B>
   </font>
  </button>
</center></tr></td>
</table>
</center>

--------------------------------------------------------------------------------------------------------------------------------------------------

Example 2

Re: SharePoint 2013 and 2019 Form Library Edge

Hilary Stoupa — Fri, 14 Feb 2020 15:55:40 GMT

In the direct link, do you include any URL params, like maybe "openin" or "noredirect"? I'm wondering if those might help here. https://docs.microsoft.com/en-us/previous-versions/office/developer/sharepoint-2010/ms772417(v%3Doffice.14)

Re: SharePoint 2013 and 2019 Form Library Edge

meissen — Fri, 14 Feb 2020 15:39:10 GMT

Thanks for the quick reply! This SharePoint 2019 seems to be quite a challenge. Since direct linking to the InfoPath form isn't working, I thought maybe my work around could be to filter the Form list on a unique value using FilterField1 and FilterValue1 in the URL - of course it appears in 2019 that doesn't work either and requires some sort of hash code in the URL for a filtered view to work. What a mess!

Re: SharePoint 2013 and 2019 Form Library Edge

oOoSLIPPYoOo — Fri, 14 Feb 2020 14:56:20 GMT

That's terrible! I'm sorry you're going through that issue. Background on what I know from my testing at this point is it's complicated....We are working to get off of Internet Explorer in Compatibility Mode as fast as possible due to security issues with IE. IE still works for me with SharePoint 2019 and InfoPath as long as IE is in compatibility mode.

At this time, in my development SharePoint 2019 environment, in a classic site, (not modern) all my forms are unable to be opened in Edge or Chrome via a HTML <a href=""></a> tag, a JavaScript link, an xml coded link, or from clicking New Item/New Document in a form library. I'm completely down in my development SharePoint 2019 environment from an InfoPath standpoint. Edge in compatibility mode should work (tested it) but security team won't allow it so I'm awaiting a fix for an Edge Microsoft product that is not working with another Microsoft product, InfoPath, currently not at end of life yet. Won't be end of life until 2026. Compatibility mode shouldn't be a solution so I'm told. I understand degradation of functionality happens as we move to newer versions of SharePoint for InfoPath, but to not have a user be able to click a form library new item/document button to open a form in the InfoPath client within SharePoint 2019 is not acceptable. Microsoft currently has an open ticket with us. It's been open for about a month almost two. If I get a solution I'll post.

Try Edge or IE in compatibility mode, add your domain to the compatibility mode listing and see if that works. Google Chrome is a lost cause unless there's a solution and I haven't found a solution yet. Also, make sure your form library settings have Open in Client set rather than let server decide or Open in Browser.

Hope I assisted and if I didn't...hopefully someone else can chime in.

SharePoint to the end!

Re: SharePoint 2013 and 2019 Form Library Edge

meissen — Fri, 14 Feb 2020 14:06:23 GMT

Hi all - just checking in; if anyone has found a solution please let me know. Our corporation upgraded to SharePoint 2019 and it has effectively broken my process I had set up. Direct links to the forms won't work anymore - giving the "cannot be opened in web browser" message. But if I browse to the form library directly then I can click the link and it opens in InfoPath Client ccorrectly.

Re: SharePoint 2013 and 2019 Form Library Edge

oOoSLIPPYoOo — Mon, 27 Jan 2020 16:00:40 GMT

Thank you. I'm not sure there's a solution other than Microsoft Edge Compatibility Mode. I tested compatibility mode since my post. Our Security Team isn't too keen on using it but it does allow the New Item links to work within SharePoint to open the form within the InfoPath client. I agree with you Chrome may not be a solution at all but Microsoft Edge Compatibility Mode may be the only solution since IE will be going away in my organization.

Re: SharePoint 2013 and 2019 Form Library Edge

Hilary Stoupa — Mon, 27 Jan 2020 15:51:06 GMT

I don't know of anything other than third party Chrome extensions may be available to help with this.... I can try to experiment later this week & see if I can find a work-around, but I'm not super hopeful. I was hoping someone else in the community would have had direct experience with this.

SharePoint 2013 and 2019 Form Library Edge

oOoSLIPPYoOo — Tue, 21 Jan 2020 18:47:53 GMT

We're dropping IE soon. SharePoint 2013 form libraries and SharePoint 2019 form libraries in Edge or Chrome do not open SharePoint Form Library form templates in the client application, InfoPath, for users to fill out. Both browsers give an error that the form cannot be opened in the web browser. Form library is set to open forms in client application by default. Any JavaScript'd link to open the form template for a new form submittal doesn't work. Any HTML link to open the form template for a new form submittal doesn't work. Is there anyway to get an InfoPath client form stored in SharePoint 2013 or 2019 to open in the InfoPath client in Edge or Chrome easily? Also, stakeholders are trying hard not to use Compatibility Mode in Edge.