Power Automate now offers a full SAP automation action set designed for SAP GUI (v7.50+):
-
These actions rely on SAP scripting, not UIA elements
-
You no longer need UI selectors for SAP
-
Examples: Launch SAP, Select SAP navigation item, Set SAP field value
Action: Switch your SAP interactions to use these native SAP actions—they're more reliable and supported.
2. Re-enable SAP GUI Scripting
If you’ve already enabled scripting, confirm that all required settings are set on both client and server. Missing script enablement can force PAD to fall back to UIA.
Tip: Navigate in SAP to Options → Accessibility & Scripting → Script and ensure scripting is fully enabled
3. Lower DPI and Adjust Display Settings
High DPI scaling can impair SAP selector recognition.
Fix:
-
Set Windows display scaling to 100%
-
In SAP GUI: Options → Visual Design → Theme Settings → Enable “Multi-monitor scaling awareness”
Then restart SAP and PAD.
4. Disable UIA Focus/Window Events (if crashes happen)
If SAP is still detected as UIA and causing PAD to crash:
-
Navigate to %LOCALAPPDATA%\Microsoft\Power Automate Desktop\Configurations\
-
Create UIAutomation.config with:
This reduces instability in your UI automation
5. Consider VBScript as Backup (Optional)
If native actions keep failing, record your SAP steps using SAP's scripting
→ Then call them via PAD’s Run VBScript action This can be more stable in some environments.
If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍.
Regards,
Riyaz
