General

Re: Customizing InfoPath error messages

ZhenYuan — Tue, 05 Oct 2010 06:46:16 GMT

Hi Patrick,

Is there a way to extend the timeout period for webservice connections across the board? I have many many webservice calls in this form, say 15. And that is why for some of the more sophiscated calls, I can get a timeout during the heavy traffic period of the day.

Regarding the "Rules cannot be applied" message, how do you stop rules from firing when there is an error and catch them according to the type of error? Is there a set of error codes?

Re: Customizing InfoPath error messages

Patrick Halstead — Wed, 29 Sep 2010 09:18:35 GMT

Hi ZhenYuan,

You can add code and catch the error and change the event, but that seems like a bad practice to me.

Some other techniques:

Change rules to stop firing on failure and/or add an alert with a different message so users know what happened.
Reduce the amount of data you are returning using DBXL's QueryBuilder and cascading dropdowns - that way you improve responsiveness of the form.
Why not just ensure there is no error? To make the timeout larger:

WebServiceAdapter2 wsAdapter = (WebServiceAdapter2)thisXDocument.DataAdapters["DataConnectionName"];
wsAdapter.Timeout = 60; // Increase to 60 seconds - Default is 30
wsAdapter.Query(); // Issue the query

Not sure if this will help a whole lot, but just thought I'd respond.

Good luck!

Customizing InfoPath error messages

ZhenYuan — Wed, 29 Sep 2010 03:52:11 GMT

Hi,

I'm just wondering if it is possible to customize InfoPath error messages? The standard message, "Some rules were not applied", isn't very intuitive and the detailed message can be rather generic and confusing to users.

Is it possible to change this message somewhere? For example, if it is a timeout issue, just inform users that it is a timeout instead of "Some rules were not applied".

Thanks