Hi there,
I’ve been looking on the Forums searching for people with the same problem I’m currently facing, but so far I have yet to see a post with the exact same situation or a solution that did the trick for me as well. Apologies if I did somehow miss a topic that covers my current roadblock.
I’m currently working on a script that enters data in the MIRO transaction in SAP. The data gets fetched from an XLS file and afterwards the script writes the data in different input fields in the SAP transaction. I’ve tested the entire process a few times successfully with the input mode of the SAP application scope being set to Hardware events.
As I was nearing the point of being fully satisfied with the current build of my script I wanted to make sure I would be able to run it in the background. I read in the documentation for that to be possible the input type of all my “Click” and “Type into” activities needs to be set to Simulated. Hence I changed the input mode of the entire SAP application scope to Simulated and I made sure to adapt for any warnings the script gave me after making the change (I had to remove the “click before typing” in a few of my “Type into” activities as UiPath gave the warning that this is only possible for activities with Hardware events as the designated input mode).
Everything seemed fine but once I pressed Debug file I was met with the error below:
At first I thought maybe this specific transaction just doesn’t support simulated input mode, maybe it’s just the way I built the script. However, once I put that specific activity on input mode Hardware events and I kept the rest of the application scope on input mode Simulated, all the other activities accepted simulated typing/clicking and the script ran successfully.
So now I have a script that works for just about 95-99% on simulated input mode, yet there is a single activity that does not want to support it. The part I don’t understand is that this specific activity is in the same transaction as the majority of the other ones I use in the script, it is an input field like all the others and it is executed in the same sequence of activities as the other UiElements. Even the descriptors look very alike, the only difference I can see is the actual ID of the element in the SAP transaction.
I’ll add some screenshots to visualize my case.
Below: 2 UiElements that are almost the same, they both have to type something in a certain field in SAP. Activity 1 gives an error when using Simulated typing, but activity 2 is OK.
I pasted them both in the UiExplorer to see if there were any inherent differences but they’re nearly identical apart from the actual ID of the field.
Because the two descriptors are so similar, I feel like it’s not that specific field that is giving me the error. Am I forgetting something else? I should add that between opening the SAP transaction the XLS file is also invoked as well as a for each activity before it starts typing in the SAP fields. I tried adding a focus activity before the “Type into” activity that returns the error, but that didn’t change the outcome.
I’d appreciate any advice I can get. I’m pretty new to working with Studio so I might just be forgetting something basic, but I can’t seem to figure it out by myself.
Thanks in advance and kind regards!