Although the name tags are the same, the id tags are different, so include the id tag in your identification of each button.
e.g. id=“ux-509748”, id=“ux-791383”, id=“ux-929420”
If the id tags change, what about using the value tag, or even possibly the formcontrolvalue tag? You need to find some reference that is unique to each.
e.g. value=“0”, value=“1”, value=“2”
Forecast: //input[@name="operationalInitiationVisaForecast" and @value="0"]/following-sibling::label
Real: //input[@name="operationalInitiationVisaForecast" and @value="1"]/following-sibling::label
N/A: //input[@name="operationalInitiationVisaForecast" and @value="2"]/following-sibling::label
@stevio052002 How does getting the label "dynamically” assist the OP of determining which label to use? The issue was not getting the labels (plural) in a different way, but to get the labels in the first place as each “looked” similar to the others.
As the OP has a solution, which was to use two attributes, thank you for your thought(s). Also, yes the OP could have used only one Object to represent the three elements using parameterization, putting the value amount as an input reference–but small steps.
You picked up this old topic which was already solved 5 years ago. Your action does not help anyone. It rather confuses others. Please stop excavating the ruins.
If you want to post something new and helpful, you should create a new topic on your own.