Saturday, May 27, 2006

InfoPath 2003: do's and don'ts

I am currently a Office - InfoPath 2003 consultant. I really learn a lot about InfoPath and its boundaries. In my opinion it's interesting to summarize some practical do's and the don't for InfoPath 2003 before you promote InfoPath as Office's wonder. Those do's and don't can be a start for a new post. ;-)

Here they are:


- Do not make applications in InfoPath 2003 with logging, historical data
- InfoPath 2003 does not support workflows
- Do not create a form with one or more views for several roles when each role or view has its
own rules. Rules are bound to data fields. So, if you use a rule on view 1, the rule will also be executed in other views. On the other hand conditional display formatting will be executed per control which represents a field on one view. So, a conditional formatting on view 1 will not influence other views.

- Do not use InfoPath as GUI + business + database
- InfoPath does not support multi – languages (if the company forbid to use several views per language)


- Create forms in InfoPath 2003 without workflows. Do not call your form an application !!!

a form to request your holiday, a form which represents a bill and calculate totals

- InfoPath is perfect to replace the GUI part of your application, but it’s very difficult to replace all layers in your application.

Use InfoPath to show and format data from databases, web services, SharePoint, …
InfoPath can be a perfect smart client which can show, send, format, calculate data … but nothing more …

- If you use different rules on the same fields for different form users (roles). I suggest to divide the form in more than one form which will separate the rules for all different users. So, there will be no rule-conflicts.

- I prefer Visual C# to write custom code. You can use the IntelliSense of Visual Studio which can reduce frustrating moments in JavaScript.