For many years, I've worked with InfoPath and SharePoint Designer to build systems and processes for clients that use SharePoint, a web-based collaboration tool that is integrated into Microsoft Office, for their customer relationship management system and project management repository. In the last couple of years, it has been transitioning to SharePoint Online and most recently using tools like PowerApps and Flows. When PowerApps and Flow were first introduced, they lacked features and functionality that was present/utilized in the tools that are now considered old and out of date. Fast forward to today and now PowerApps has taken on lots of the functionality that InfoPath was used for. Microsoft Flow can handle a lot of the workflows that seemed to only be possible through SharePoint Designer, a strong coding background and lots of patience. CMS Wire posted an article titled, and in it they talk about the upcoming sunset of InfoPath and SharePoint Designer.

Access For Mac Free Trial

InfoPath has been 'going away' for quite some time now and there is now a firm date. I have mixed feelings about the lost of two of my favorite SharePoint tools. As a Mac users, being able to use PowerApps and Flows through a browser without having to install Windows OS on my machine or keep a PC for the sole purpose of SharePoint development, is pretty great. However, I still wonder if features and functionality will be lost. I'm excited by how much PowerApps and Flows have evolved since the first I used them. One comment in The Evolution of the SharePoint Citizen Developer speaks to the learning curve. As someone who develops in a few different content management systems, proprietary and open source, SharePoint was always one where it kinda felt like I had to think of things opposite to everything else.

I will take note of this as I begin the process of converting or should I see re-imagining the flows and forms taking them from InfoPath and SharePoint Designer to PowerApps and Flow. I'd love to know your thoughts of the. I found it helpful especially the list of primary Microsoft Tools past and present, did you? Are you using other tools/apps to replace SharePoint Designer and InfoPath? I'm curious to know your experience, add a comment below or us. For additional information:.

InfoPath 2013 InfoPath 2010 InfoPath Forms Services is a server technology that allows users to fill out Microsoft Office InfoPath forms by using a Web browser. Users don't need InfoPath installed on their computers to fill out an InfoPath form, nor are they required to download anything extra from the Web. All users need is access to a browser, such as Microsoft Internet Explorer, Apple Safari, or Firefox.

This article lists the browsers that are compatible with InfoPath Forms Services. In addition, this article lists the features that are supported in browser-compatible form templates, the features that cannot be used in browser-compatible form templates, and the differences in behavior that may occur when forms that are based on browser-compatible form templates are viewed in different browsers. In this article Web browsers that are compatible with InfoPath Forms Services = Full support = Partial support = No support. Note: If a specific browser version is not listed in the following table, it is not supported. For example, there is no support for older browsers, including Internet Explorer 5.01, Internet Explorer 5.5.x, Internet Explorer for Macintosh, and versions of third-party browsers that are earlier than the ones that are listed in the following table. Although it is possible that browser-enabled forms may function correctly in these browsers, browser-enabled forms have been tested only with the browser versions that are listed in the following table.

The following table shows the specific browsers that are compatible with InfoPath Forms Services. Browser Windows 1 Unix/Linux Macintosh Microsoft Internet Explorer 6.0 (32-bit) Windows Internet Explorer 7.0 (32-bit) Firefox 1.5 Mozilla 1.7 Netscape 7.2 Netscape 8.1 Safari 2.0 1Includes Windows Vista, Microsoft Windows Server 2003, Microsoft Windows XP, and Microsoft Windows 2000. InfoPath features that are supported in InfoPath Forms Services Most InfoPath controls and features work identically regardless of whether users are filling out a form in Internet Explorer, Firefox, Safari, or any other supported browser. However, the same form may appear differently in different browsers. These visual differences can be attributed to the way that the various browsers support Web technologies, such as Hypertext Markup Language (HTML), cascading style sheets (CSS), and JavaScript.

In addition, there are some controls and features that are fully supported only in browsers that support Microsoft ActiveX technologies, such as Internet Explorer 6.0 or Internet Explorer 7.0. In other browsers, these features may behave differently or have limited functionality. Support for form controls You can use the following table to determine whether a particular InfoPath control is supported by InfoPath Forms Services. In some cases, even if the control is supported by InfoPath Forms Services, it may not work the same way in all browsers. For example, you can use rich text boxes in browser-compatible form templates.

However, users only see the full range of rich text formatting options when they fill out the form in Internet Explorer. Similarly, when users view a form in a mobile device browser, some controls appear differently than they do in a desktop browser, and some controls are ignored completely. For example, although you can use a file attachment control in a browser-compatible form template, this control will not appear when the form is viewed in a mobile device browser. For more information about optimizing form templates for use on mobile devices, refer to the See Also links at the top of this article.