Well, now that we have the complete question, perhaps we can get you a complete answer!
You can tell the name mapping to use a project variable. Build the variable as I described before and assign that variable in this dialog.
Well, now that we have the complete question, perhaps we can get you a complete answer!
You can tell the name mapping to use a project variable. Build the variable as I described before and assign that variable in this dialog.
Thanks, This works.
OK, After getting this working I wanted to post What I actually did.
I was not able to create the project string variable the way that Marsha_R described.
""beginningoflinkgoeshere"+Eval(referencetoexcelgoeshere)+"endoflinkgoeshere""
I consistently got an error whenever I used the Eval function in the "Set Variable Value" dialog.
Inside of a script this may work just fine.
I also could not concatenate the value from my table data with any other string in the "Set Variable Value" function.
To get this to work I created a variable with just the table data in it.
After that I was able to create the variable with the string that I needed.
'//a[.="'+Project.Variables.SearchResultsTitleString+'"]'
To set the locator property, I used the following. %SearchResultsTitleLocator%
NOTE: you do not use the "Project.Variables." prefix when referencing the variable here. It is expecting this to be a project variable. Adding the prefix will cause a runtime error. Also, you have to enclose the variable name with "%".
Now when I run my test, I can select the list element by the title name and get the specific Item that I am looking for.
Winner Winner Chicken Dinner !!!
The following documents were very helpful.
