Microsoft InfoPath

» see office.microsoft.com/infopath as it lived, on the wayback machine

~ the eulogy ~

by the time i would have signed up to infopath, there was no reason to sign up. it was a tool you got because your it department deployed it for sharepoint, and the only people in my orbit who touched sharepoint forms were systems people inside large enterprises with a microsoft licensing relationship.

to be fair, infopath was a decent answer to a real problem. before it shipped, the way you collected structured business data was usually a word document with bracket fields, or a custom asp.net page, or a paper form scanned and rekeyed. infopath let a non-developer drag fields onto a canvas, save the form as an.xsn file, and have the result publish to a sharepoint forms library with the data stored as clean xml. it shipped with office 2003 on the 21st of october 2003.

i was a university student in turkey when it launched. infopath was not on the radar of anybody i knew. ttnet broadband was barely deployed in 2003. msn messenger was the chat layer. for a microsoft enterprise tool aimed at the sharepoint admin tier, ankara was not the target market.

microsoft announced on 31 january 2014 that infopath was discontinued and that no further versions would ship. the infopath 2013 client got an extended-support window through july 2026 so that the big enterprise customers with thousands of legacy.xsn forms had time to migrate. the announced replacement path was powerapps for the form-builder use case and microsoft forms for the lightweight survey use case (or whatever it was called).

~ the dossier ~

~ what it actually did ~

the infopath designer was a windows-only thick client. you opened it, dragged controls onto a canvas (text fields, drop-downs, repeating sections), bound them to an xml schema you either imported or had the tool generate, and published the result to a sharepoint document library. an end user could then open the form in either the infopath filler or, after sharepoint 2007, directly in a browser through infopath forms services.

the appeal was that you got a forms-engine without writing a single line of code. data validation rules were configurable in the ui. conditional formatting worked through a wizard. workflow connectors hooked into sharepoint approval lists. for the sharepoint admin who had been writing custom infopath alternatives in asp.net forever, it was a real productivity win.

~ the long tail ~

the extended-support deadline of july 2026 was the actual end-of-availability for organizations that never migrated. there are still production sharepoint farms in 2026 running infopath forms because the rebuild cost on a custom.xsn form with a decade of business logic baked in is not trivial. powerapps does what infopath did, but the migration is a rewrite, not a port.

in the broader microsoft graveyard, infopath sits alongside frontpage and office live workspace as a piece of the early-2000s office vision that the cloud-first roadmap quietly retired. for whatever reason, microsoft never replaced it with a single direct successor. the form-design problem got split across powerapps, microsoft forms and the sharepoint list designer. that fragmentation is part of why the july 2026 deadline still has organizations scrambling.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »