I’m working with UIPath to automate some processes in Microsoft Dynamics AX 2012. When I use UIPath to indicate a button to press or a field to type into, UIPath gets a brainfreeze (stops working) and just chews on it for 3-6 minutes before it has completed. It works, but it take a ridicolous amount of time to make a process, as this is the case at every click. There is no problem when the process is running from orchestrator - it is only during development and only in AX. In all other programs it only takes a split second.
Does anyone know what causes AX to be this slow and how to fix it?
Hi! It shouldn’t matter. the processes are running fine when first published. It is during the development it takes time to indicate what the robot should press
Yah that’s fine
Kindly try enabling Them and let know pls
Because usually from being orchestrator the process runs much faster than from the studio as it is called as a Windows service
AX requires you to switch the UI Framework Type to AA
Steps 1) Make sure the mouse is not hovering over AX
2) Click “Indicate Element”
3) Enter F4 (1 Time)
4) The UI Framework type should have changed from default to AA
5) You should now be able to hover over AX without fear!
6) Stretch, relax, drink some coffee/water/tea
7) Have fun developing!
