Rules that usually scaffold well
Switch view
Maps naturally to Navigate(...) when the target is a generated screen.
Set field value
Can become defaults, button OnSelect assignments, or form update formulas depending on context.
Show / hide
Can become Visible formulas or virtual screens for single-view forms that hide sections.
Rules that need builder review
- Rules with complex XPath conditions or nested dependencies.
- Rules tied to code-behind, script, or unsupported event handlers.
- Submit rules that call external systems or use non-SharePoint destinations.
- Role-based logic that depends on legacy InfoPath user roles.
Review workflow
Open the Rules tab
Look for partial and manual-review items first.
Confirm the target property
Decide whether the rule should affect Visible, DisplayMode, Default, Update, or OnSelect.
Test in Power Apps Studio
Use sample data and preview mode to validate the behavior after import.
Common questions
Can InfoPath rules be copied directly into Power Apps?
No. InfoPath rules use a different model. The converter turns recognized rules into Power Apps-friendly scaffolds and notes.
What happens to script rules?
Script and code are flagged for manual review because they need a replacement implementation.
Should rule behavior match the original exactly?
Business behavior should match. The Power Apps implementation may be cleaner if old view and show/hide logic is redesigned.