It should always be possible to identify any element without reverting to code (using Blue Prism is supposed to be a move away from difficult to support bespoke scripting). If you are ever about to use code stages instead of Application Modeller please chat to your Blue Prism mentor/expert first to ensure there is not an easier way.
I would recommend you contact your Blue Prism mentor if you are having trouble identifing an element uniquely as he will have more practice. If you haven't already read it, I recommend the Browser Automation Guide in the learning area of the portal, also it might be worth seeing if the other option on the Identify button (the navigator option which brings up a treeview of the model) gives you any other elements to identify.
Don't forget, you can change the number on match index to be other than 1, you can also use x and y (or parent x, or ax etc) coordinates in a more dynamic/robust way by using > or < - i.e. and dyncamically based upon the position of a nearby label (which you will be able to spy uniquely because if it's text, and retreive its bounds).
