Skip to main content

Does InfoPath (still) suck?

A couple of years ago, I wrote a blog post titled "InfoPath & SharePoint (Part 1)". Back then I had just started working on a project using InfoPath 2007. So, expectedly, the post wasn't very complimentary to InfoPath (or SharePoint). In fact, I said:
InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment, has absolutely no redeeming value. It's worthless.... (more)
Since then my opinion of InfoPath has changed slightly. It still suffers from all the flaws I pointed out in that post. However, I think when used right, InfoPath can be an OK tool. I think it's well suited for designing one off forms and not for anything that requires complex logic or multiple iterations (like most software development requires). Alas, most CTOs fall in love with its point & click simplicity and integration with SharePoint that they try to use it to replace more developed technologies like ASP.NET. What do you get? A horrible development environment that's absolutely not suited for software development and highly paid software developers designing InfoPath forms. See this link for an an example of how InfoPath makes something very simple and basic very complicated.

With the 2010 version, there's been many nice changes to InfoPath. But it still makes me chuckle that a Google search for "InfoPath sucks" turns up my blog post.



  2. I've 8 years of ASP.NET C# experience out of 20 years in software development and abour 27 years as a programmer of some sort. I've spent 3 years working with SharePoint mostly 2010 and I basically trust my own judgement above anyone elses of a technology.
    I've had a few projects where InfoPath was inflicted upon me and the odd occasion where I'd choose it. Basically I agree completely with your assessment, InfoPath is just sophisticated enought to trick the unwarey into using it for forms that need a fair bit of logic with them and thats where it fast becomes a complete nightmare. I'm at the end of 3 days bending InfoPath to my business requriement where I would have been done inside 3 hours with ASP.NET. C# FormCode mixed with list event handlers and front end InfoPath "Rules".... it's beyond a joke. Oh and they never got around to implementing Managed Metadata taxonomy fields into InfoPath either....
    "InfoPath is crap" comes straight to this page too by the way ;)

  3. It is an absolute POS.

  4. Right now, I'm burning midnight oil to finish the external list's custom form in InfoPath. More precisely I'm in the middle of trying to figure out why I even took this job.

    To calm my nerves with some rants I googled "InfoPath sucks". I'm hoping it'll help :-)


Post a Comment

Popular posts from this blog

The Teenage Years Cometh

If you're lucky, a few days after your twins are born, the hospital just let's you walk out with them. In fact, they insist you take them with you. No training, no classes, no probation...they really just let you walk out with 2 humans. #fatherhood — Tundey A. (@realtundey) November 28, 2021 This was me 12 years ago: And now look at them. In a little over 6 months, they'll be teenagers!   Every time I look at them, I am reminded of Obama's quote on being a parent:  "One of my favorite sayings about having children is it's like having your heart walking around outside your body." — @POTUS — White House Archived (@ObamaWhiteHouse) October 21, 2015

InfoPath & SharePoint (Part 1)

A departure from sports and politics. This one is about technology. InfoPath sucks and SharePoint is the most expensive piece of crap ever. InfoPath, as a development environment , has absolutely no redeeming value. It's worthless and if your boss ever thinks of using it, you have three options: convince him not to (not easy once he's been brainwashed by the Microsoft marketing presentations) use one of Al Gore 's lockboxes to store away your sanity 'cos you'll lose it. Also, pad your estimates very generously . You'll need every bit of time you can get. quit immediately while you still have your sanity First, InfoPath: To me InfoPath is like programming in assembly language . Sure it makes it easy (too easy in fact) to bind data to controls. But it doesn't provide you with easy access to your controls. Why is this important? Say you want to disable a button : in most technology: buttonA.enabled = false (or something similar). In InfoPath, you simply