Hi POOMAL001,

The "Send Keystrokes" command seems to be working for now. I did notice that while I am in debug mode the bot will run through 3 entries and then "Cancel" out on its own. I have a screen snip of this but I am unsure of how to share it with you or your team.

Hi UMAASH001,

As per my understanding, the validator is showing the correct field. If set text command is not working, try using first Desktop click element command or(Desktop send key command) to bring focus on that textbox. Second step would be to use Send Keystrokes command under Input - where you need to specify the window name, text to send. In case you are using any special keys, you can enable the interpolated keys to yes.

1. Text to set � �xyz{ENTER}� (Example text � xyz)
2. Enable interpolated keys � Yes In case there are no special keys, then you can set enable interpolated keys to No.

Please let me know if it worked for you.

Hi POOMAL001,

I have made sure that the attributes are accurately identified, I have de-selcted the "Name" attribute on all elements. the Validator is showing me that the correct field is being targeted. For the set text command, how can I check to see if the program will allow me to set text? the best way I can assume this is that I am able to copy and paste data into the program, outside of the automation. Normally we take the data from the spreadsheet and either enter it by hand or copy and paste into all the fields. I am still using the same legacy software that is built on Visual FoxPro Version 9.0 Service Pack 2 (SP2). If need be we can set up a video call to try and work this out together.

Hi UMAASH001,

If the Desktop Set Text command doesn't work and the reason for your error - Set text only works on controls that allow you to set text, because it modifies the control directly, it doesn't automate key presses. If the control doesn't allow it, it fails. Alternatively, you can use other commands such as - Send Keystrokes, Send Key commands to set the text in your application.

Please let me know in case you have any query.

Hi UMAASH001,

Its good to know that the recorder is identifying the elements. I would suggest that before identifying any elements, please active the window once using Activate Window command. Then proceed with identifying the username textbox. The reason for your error could be there might be some attributes that are not identifying the text box correctly. I would suggest you to select dynamic attributes such as - Automation ID, ClassName etc. and use UI Element validator, to validate your textbox. In set text command, make sure the click element is set to No. In case you are using keystrokes, please set enable interpolated keys to yes. Please let me know if the application you are using is public , so we can test it from our end as well.

Hello POOMAL001,

I recently tried to debug the the bot, and it no longer is setting the text as previously mentioned. The permissions levels are the same, the recorder is identifying the elements, and the "Name" attribute is deselected. I have not changed anything for this bot since our last conversation either. I keep getting the error now "Source: 'C:\Users\umaema.a\Documents\OpenBots Studio\OB Scripts\DesktopAppLandPro\Main.obscript', Line: 6 - 'Desktop Set Text [Text '"umaema"' - Element Name '"txtUserName"']', Type: 'InvalidOperationException', Message: 'Operation cannot be performed.'"

Running openbots studio as admin does allow the recorder to identify elements! It is working on the login page so far, I will update you if there is any issue with the recorder further along the line. Thank you so much!

Hi UMAASH001,

For the issue mentioned above, if would suggest that the application and open bots studio should be both at same access level. If the application is in administration mode, please launch the Open Bots Studio in administrator mode. Try to record and please let me know if it worked for you.

Hey POOMAL001,

Thanks for getting back to me! The program I am using is called LandPro which is built on Visual FoxPro. I would assume that it is on the latest version for VFP. Unfortunately it is dead and the application LandPro itself is a legacy system.

I see your suggestion to provide inputs to the properties in the "Desktop Set Text" command. This would only be possible if the recorder was actually recording. The recorder is not registering the click on elements. - I have changed the permissions on the application to not run as administrator, and then the recorder begins to register clicks on elements. But the issue now is that the application is required to be run as administrator. Without administrator privileges the application does not function as it should.

It does work with other applications, so long as they are not being run as administrator. I have tried recording elements in AWS and it works fine until I run as administrator. At that point it does not record. Is there a way to get the recorder to work while in administrator mode?

I will be testing out the surface/image commands to see if they can help, but I strongly feel that the desktop commands will be best for functionality.

Hi UMAASH001,

Additionally, as per the compatibility issues may I know if it is working fine with another application, like notepad. Just to test if it is a compatibility issue with the target application or an issue with the recorder. Also, if the application doesn�t generate selectors/attributes , it could be processed like an image. We have surface automation/image commands available as well. You can try them out as well.