Hi Sfeger and welcome to the Silk Performer forum. The XPath locator string which you highlighted, would not be recognised as a valid XPath locator to uniquely identify the element on the page. However, there are different approaches you can take to address the scenario. 1. You mentioned that there did not seem to be no other Property / Values which would uniquely identify the element, to confirm this, I would highly recommend adding the ‘id’ attribute to the ignored DOM attributes name list within Silk Performer – SILK PERFORMER | SETTINGS | ACTIVE PROFILE | WEB (BROWSER-DRIVEN), carry out another recording against the application, interact with the checkbox and see what XPath locator string is generated. The following kb article explains, Xpath locator strings work in Silk Performer: community.microfocus.com/.../555.preferred-dom-attribute.aspx 2. Depending on the elements on the screen and which element you wish to interact with, you could possibly use the syntax such as //INPUT[1], which means the first element which uses the HTML input tag is selected, of course the parameter [1] can be customized to suit your needs. Example BrowserCheckBoxSelect("//INPUT[1], CHECKBOX_CHECKED); The problem here is the input tag would not only be used by checkboxes but also text boxes etc. So there maybe an issue in uniquely identifying the element you wish to choose. Regards Paul
↧