Hi. Actually, what you are running into is by design. PowerBuilder with UFT behaves a little differently than other apps you might have worked with. It sees the toolbar as one object, and then records on coordinate clicks within that parent object to choose the selection. Take a look at the UFT Addins guide PowerBuilder section under ''Known Limitations/Troubleshooting'' and the end of the chapter. It will explain it.

Thanks! I did find that in the guide. However, I'm also seeing that when I try to work with a form, it's only capturing the PBDataWindow object and nothing else? I don't see that in the guide?

Yep. That's another known limitation of the PB addin with UFT. Although it's not mentioned in the Addin guide, it has been around for a while and is documented on HPE's support knowledge base site. I won't post the article here because you'll need to log into HPE's site to find it anyway, but do a quick search for UFT and PBDataWindow and you'll find the article as the first link.

What happens is that UFT identifies the PBDataWindow as a table, and all of the objects inside of that table are cells. Every edit field is a cell (like in a spreadsheet for instance) and you can navigate them by methods such as SetCell, GetCell, etc.

I think it will make sense when you read the KB on their website and you can easily work around the issue just like you would a WebTable or similar object.