The quickest way to see what works is to record a short test where you type in that box and see what code TC gives you in the test it creates.
Yes that is what I tried at first.
When recorded, the test does a click in the field, then enters the value. This works, but I wanted to avoid the clicking the field in case it changes to a different position (also timing issues and things like that sometimes don't make the cursor/clicking reliable).
When recorded and converted to script, it doesn't use the aqObject.SetPropertyValue.
I thought that by setting the property that way, I could avoid the clicking in the specific field.
