Search
Web Braintrove
Site Navigation
Home
Products
Tags
Levels
Dates
Authors
5 MOST RECENT
Locate Conditional Formatting and Custom Validation in InfoPath 2010
Conditionally Display Different Values In a Single Expression Box
Create a Button With a Blank Label
Create Shared Rules
Perform a Case-Insensitive String Comparison without Using Translate()
5 MOST POPULAR
Access a Method in a Master Page with Code-Behind
Pass Query String Parameters to an ASP.NET Xml Control
Prevent Namespace Prefixes from Being Copied to the Output
Create Groups in a Drop-Down List Box
Configure IIS 7 for Custom Error Pages
5 MOST FORGOTTEN
Create a Rusted Text Effect Using Styles
Convert Between Time and Decimal
Install Windows 7 Beta onto a Virtual Machine
Create a Drop Cap Using CSS
Enable Themes in Windows Server
Microsoft MVP
This article has been viewed 151 times.

Debug Rules Using a Break Rule

Written by Gregory Scot Collins
Wednesday, 4 March 2009, 2:57 PM
This article has been tested to work with the following products and versions. No guarantee of compatibility, with or without modification, is offered for products or versions other than those listed.
Debugging rules in InfoPath can be quite exasperating as InfoPath does not provide an easy way to identify issues. If you have multiple rules on a control and something is not working as expected, you can narrow down which rule is causing the issue by creating a Break rule.
A Break rule has no conditions and no actions—its only purpose is to break the flow so that following rules are not processed. A Break rule is temporary and is discarded after debugging is complete.

Create the Break rule

You create a Break rule with the following steps:
  1. Right-click the control with rules that need debugging and click Properties.
  2. In the control Properties dialog box, click Rules.
  3. In the Rules dialog box, select the first rule, and then click Add.
  4. Name the rule BREAK.
  5. Select the Stop Processing Rules When This Rule Finishes check box, as shown in Dialog 1, and then click OK.

Debug using the Break rule

If you selected the first rule then the Break rule was added as the second rule in the list. You can either begin debugging here, or if you know certain rules are working fine, you can move the Break rule down the list by selecting it and clicking Move Down.
To debug using the Break rule, preview or launch your form, and then perform the action that will cause your set of rules to be processed. InfoPath will stop processing the rules when it encounters your Break rule. If the issue does not reproduce, go back to the designer and edit your rules. Move the Break rule down the list by selecting it and clicking Move Down. Try reproducing the issue again. Continue moving the Break rule down the list until the issue reproduces. At this point you have found the issue rule—it's the one just above your Break rule. Now you can debug the actions for that rule.
When you have finished debugging, you simply remove the Break rule. You can use this technique any time you run into issues with rules that are not easily identified.
Bookmark this Article
StumbleUpon  Stumble It!
Digg  Digg It!
del.icio.us  del.icio.us
List of Figures
Dialog 1 - A Break rule has no condition or actions.
Article Tags
Great Deals
TigerDirect Exclusive Deals, Limited Time Offers, Act Now And Save!
Find all current special offers on Adobe products.
Try SugarSync Free!
Join WebHost4Life.com
TigerDirect
Computers4SURE (4SURE.com - An Office Depot Co.)
Copyright © 2006-2010 Braintrove. All rights reserved. Braintrove, braintrove.com, and the Braintrove logo are trademarks of Gregory Scot Collins in the United States and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners. Any rights not expressly granted herein are reserved.