July 30, 2014 by spjeff
Microsoft announced InfoPath will go away in 2023. It makes sense and they have good reasons. However, form developers are confused about available options. I have an idea for the InfoPath Roadmap and would appreciate your feedback in the comments below or Twitter (@spjeff) please.
When people say “InfoPath” they generally are referring to a three part system outlined below. InfoPath strictly speaking is the form input experience. Form Library holds the saved XML output. SharePoint Designer can then trigger email notifications based on status change.
DEV1 > “Hey did you hear Microsoft is retiring InfoPath in 2023?”
DEV2 > “Yeah, but it’s all we have today so I’ll keep using it. Not sure what else to use. Sure would be nice to have HTML5 and cooler input experience.”
DEV1 > “Definitely. Coding from scratch is a lot of work. I don’t really want to mess around with SPList REST connections for CRUD or make a SQL database with SVC/OData for simple forms. My head hurts.”
DEV2> “True, but I guess we’ll gave to make a schema first then form later.”
DEV1 > “InfoPath saved as XML. I like XML. It works well for import/export across all of our systems. Could we keep XML but ditch InfoPath?”
DEV2 > “Cool idea, but I’m not sure how.”
Why throw out the baby with the bathwater?
Can’t we make fantastic forms with HTML5/JS and then save back to a Form Library in order to leverage SharePoint for storage, views, and workflow? Right now this is just an idea. I don’t yet have a working prototype to show but think it would be straightforward to convert JSON to XML and upload. InfoPath would still be used but by developers for schema only (define XML structure). End users would never see it.
Please leave a comment below and let me know if you think this might be practical. Thanks!