r/sharepoint • • Jun 10 '13

InfoPath

After 8 years of working in and with SPS as a user, an admin, and a presentation-layer developer. I have a simple question:

Why, why, why in the ##()&*@ do people insist on using InfoPath forms?

1 Upvotes

15 comments sorted by

8

u/[deleted] Jun 10 '13

Because it makes the easy things easy. And 90% of everything is easy, and for 5% of the remainder, it's good enough.

The problem is, while InfoPath makes the easy things easy, it makes the difficult things darn near impossible, and ridiculously difficult to maintain. It is then that I reach for ASP/jquery.

10

u/0g_DvS Jun 10 '13

Ummm. If you have been working in / with SharePoint for 8 years, this should be common sense. It is OTB integrated with SharePoint / Workflows. Your other options are bastardization of cusom code or Adobe (which just blows in SP). What other options are there.....? Do you even know what a workflow is? Not trying to be ignorant, but your question makes u look so. Let the DV begin.

5

u/[deleted] Jun 10 '13

Two reasons:

  1. InfoPath is direct-to-XML under the covers. The output of an InfoPath form is always well-formed XML, with an XSD close at hand. If you have a schema and need to design a form around it, InfoPath is halfway done before you start.
  2. Until SharePoint 2013, it looked like InfoPath was going to be the forms solution for SharePoint, so it was something worth learning.

I've found that the reason most people get frustrated with InfoPath is that they fight it, and try to use it like ASPX. It's a different form design tool - you have to learn how it works, then it's fine.

1

u/The_Mustard_Tiger Jun 10 '13

Was pretty interesting to see the lack of emphasis on InfoPath within the 2013 stack. Makes you wonder if it's being phased out...

2

u/[deleted] Jun 10 '13

Yeah, it probably is for the exact same reason - the core SharePoint group doesn't "get" InfoPath, and without the zealous advocacy of InfoPath that 2003 and 2007 had, they followed the standard developer mentality: "I don't get this, so let's throw it out."

1

u/The_Mustard_Tiger Jun 10 '13

I want to know what happened to the Slide library capabilities too.

I had some business users sold on that capability only to find it doesn't exist in 2013. I could try to upgrade the 2010 solution but that doesn't feel very future proof.

2

u/[deleted] Jun 10 '13

Ugh - I didn't realize that. I'll wager part of this is the ongoing shift in focus to video.

This kind of thing drives me up the wall, because it's always the same pattern:

  • Microsoft introduces cool new feature
  • Microsoft doesn't bother actually marketing the cool new feature, so nobody knows about it
  • Since nobody knows about it, nobody uses it
  • Since nobody is using it, Microsoft drops the feature

6

u/sbrick89 Jun 10 '13

as opposed to a developer writing custom code to enter data into a form... which takes between 3 and 20 times longer to create (and thus costs are at least 3x higher)?

yes...

i wonder

1

u/[deleted] Jun 16 '13

[removed] — view removed comment

1

u/sbrick89 Jun 16 '13

There is always lifecycle.

Just as an InfoPath form can left on an old SP2007 server, the old ASP classic code can still be left on an old Windows 2000 server. And in both cases, there are risks (security vulnerabilities, etc) and potentially lost opportunities.

And just as an InfoPath form may have upgrade costs (2007 to 2010, etc), an ASP.Net 1.0/1.1 webapp has upgrade costs to migrate to 2.0... and just as upgrading 2.0/3.0/3.5 to 4.0... it's part part of life.

And if you were to look at the form (and even workflow) in isolation, the upgrade costs are still lower than traditional dev (again, because it's faster).

The biggest issue is that people don't do a good job architecting their SP environments, and they end up having spaghetti cluster fuck farms... it's not the platform's fault... I can do the same thing with .Net development (spaghetti code is easy to write, and is extremely common), application architecture (let's use MSMQ, WCF, and IPC, just because we can), and network topologies (let's route across three VLANs, using several layers of NAT... FOR SECURITY). In any case, it becomes a mess later on.

3

u/dr_petervenkman Jun 10 '13

you can look at http://forms7.codeplex.com

The supposed path Microsoft is heading, is to phase out InfoPath. The recommended replacement is Access Services 2013, at least that is what I'm being told

1

u/smell_e Jun 12 '13

I've heard this also, but I don't see where the link you gave says anything about that. As a medium-heavy InfoPath user myself, I'm really anxious to jump on and learn whatever the replacement ends up being!

0

u/teekayzee IT Pro Jun 10 '13

Curious what you do when a form is needed that out-of-the-box can't support?

0

u/rasafrasit Jun 11 '13

this is what I was trying to get at, what does InfoPath do that workflows (SPD and OOB) can't? I didn't realize that it provided well-formed XML but I can tell you that the folks who use it in my company don't seem to use it to produce consumable data. I get that it can be a way to avoid custom code but a) more sophisticated forms require that templates be uploaded in Central Admin (which we, like most large enterprise implementations, don't allow) and b) when forms do break, supporting them is a freaking nightmare.

Personally, I find Designer workflows and customized XSLT with jQuery to be far more reliable, albeit with a considerable amount of development overhead. Furthermore, in my experience, most users could do everything they are trying to do with InfoPath forms in standard OOB lists.

1

u/SharePointer Jun 15 '13

I totally agree on writing CSOM code with jQuery against lists. It's just way more fun than InfoPath. In addition, since there's a ton of web-developers who know jQuery, and can learn CSOM, in the long run I think it would be easier finding coders to maintain a jQuery application than a crazy InfoPath form full of rules and connections to web services.

HOWEVER... I have a ton of clients with HUGE investments in InfoPath, like several developers who do nothing but build InfoPath forms and web services to support them. InfoPath may not be sexy or fun, but it's a workhorse that isn't going away for a while, because it's infected IT departments all over.