Thanks for the feedback. I could have set it up incorrectly, but I don't think so. Here's what I did.
I opened the drop-list and mapped the objects of it. The drop-list isn't a typical drop-list. It's a 3 column table that is dynamically generated on the fly depending on user/privileges/server and other info. Column 3 (index 2) contains the cells that have the most unique info, so I'm mapping the object on this cell. I created a Project Variable called "FormTypeFromDataSheet" that is assigned the FormType from the Data file.
Object mapping info:
Sys.browser.WebApp.panelCreateformpanelbg.frameCreateformpaneliframe.table.cell.table.cellFormType
Object attributes:
ObjectType: Cell
ColumnIndex: 2
outerText: (Project Variable, FormTypeFromDataSheet)
Here's why I think I set it up correctly.
Scenario 1:
DataFile
Run | FormType
Y | FormNameA
Y | FormNameB
Y | FormNameC
N | FormNameD
N | FormNameE
When I run this the first time through the inner loop that iterates through the forms it works for FormNameA, and when it gets to FormNameB the object tells the Click action to click on FormNameA, and when it gets to FormNameC the object tells the Click action to click on FormNameA again. I have Log Messages to output the value of FormTypeFromDataSheet and it is correctly iterating from FormNameA to FormNameB and then to FormNameC.
Scenario 2:
DataFile
Run | FormType
N | FormNameA
Y | FormNameB
Y | FormNameC
Y | FormNameD
N | FormNameE
When I run this the first time through the inner loop that iterates through the forms it works for FormNameB, and when it gets to FormNameC the object tells the Click action to click on FormNameB, and when it gets to FormNameD the object tells the Click action to click on FormNameB again. Again the Log Messages show the value of FormTypeFromDataSheet and it is correctly iterating from FormNameB to FormNameC and then to FormNameD.
Scenario 3:
DataFile
Run | FormType
N | FormNameA
N | FormNameB
Y | FormNameC
Y | FormNameD
Y | FormNameE
When I run this the first time through the inner loop that iterates through the forms it works for FormNameC, and when it gets to FormNameD the object tells the Click action to click on FormNameC, and when it gets to FormNameE the object tells the Click action to click on FormNameC again. Again the Log Messages show the value of FormTypeFromDataSheet and it is correctly iterating from FormNameC to FormNameD and then to FormNameE.
So from these results I gather that the object is set up correctly. If the FormNameA information is hard coded then I would think that Scenario 2 and 3 would be choosing FormNameA each time instead of FormNameB and FormNameC respectively.
This makes me think that the Object is correctly grabbing the variable information at the beginning of a test run, but it doesn't look like it's changing the object attribute (Project Variable, FormTypeFromDataSheet) between iterations of the Data-Driven Loop.
Any other ideas?
