Builder review8 min readUpdated June 5, 2026

How to review the Rules tab

Understand switch-view, show/hide, set-value, submit, close, and script/event-handler rule rows.

Quick answer

In short

The Rules tab shows what InfoPath was doing behind the scenes. Use it to validate generated navigation and identify logic that still needs Power Fx or Power Automate.

Most likely cause

Rule rows can look repetitive because InfoPath often repeats the same button pattern in several views or sections.

What to do next

Group rules by action type: navigation, show/hide, set value, submit/save, close form, and manual script.

Rule types you will see

  • Switch View: usually becomes Navigate(screen, ScreenTransition.None).
  • Set Value: may become a default, OnChange, OnSelect, or helper formula.
  • Submit: usually becomes SubmitForm or a Power Automate follow-up depending on the data source.
  • Close document: generally becomes Navigate back or a builder-review note.
  • Script event handler: detected but not converted automatically.

What action details mean

Action details are the useful part of the row. Look for the target view, target field, value being set, or submit connection. Generic rule labels alone are not enough to understand the behavior.

When a rule is safe to trust

  • The source and target view names are both present.
  • The target field exists in the generated screen or SharePoint mapping.
  • The condition is simple enough to express in Power Fx.
  • The imported app shows the expected OnSelect, Visible, Default, or Update formula.

Keep reading the next most relevant guides for this form pattern.