Solved
Help with a dataloop within a dataloop
Good afternoon… First let me preface this by stating that I am not a developer. That being said, I am writing a web-based Keyword test that basically tests an automated ordering application. Th...
Forum Discussion
Hi Marsha_R
I'm still struggling with this. I'm still not quite understanding how this can be done with one loop.
The PO Create process relies on 2 screens...
- The first screen is where the user enters the Vendor# and the Warehouse the product is to ship to. Once the Vendor and Warehouse are entered the user navigates to the next screen in the workflow via a NEXT button.
- The second screen is where the item# and quantity are entered. The user remains on this screen and enters items and quantities unlil they have completed the item entry process for the current vendor, (no more items for this Vendor# on the datasheet) at which time they create the PO (PO CREATE Button).
Once the PO has been created, the User returns to the first screen (Create Another PO Button) and start this process all over again, returning to the first screen and entering the next Vendor# and Warehouse.
With one loop, wouldn't this force the application to return to the first screen after each item and quantity is entered? If so this will not work. The application does not behave this way. This is why I am thinking a second loop is required where if CurrentVendor = LastVendor, the second loop repeats until CurrentVendor < > LastVendor, then loop2 ends, the PO is created, and loop1 iterates to the next Vendor# and Warehouse.
The sedcond part of my question is regardless of one or two loops, how do I go about setting the values of CurrentVendor and LastVendor? I'm familiar with the Set Variable Value statement in the Keyword test, but not sure what the syntax for those variables should look like.
Thank you again for your help!
DC.
DCat1223 wrote:
The PO Create process relies on 2 screens...
- The first screen is where the user enters the Vendor# and the Warehouse the product is to ship to. Once the Vendor and Warehouse are entered the user navigates to the next screen in the workflow via a NEXT button.
- The second screen is where the item# and quantity are entered. The user remains on this screen and enters items and quantities unlil they have completed the item entry process for the current vendor, (no more items for this Vendor# on the datasheet) at which time they create the PO (PO CREATE Button).
Once the PO has been created, the User returns to the first screen (Create Another PO Button) and start this process all over again, returning to the first screen and entering the next Vendor# and Warehouse.
With one loop, wouldn't this force the application to return to the first screen after each item and quantity is entered? If so this will not work. The application does not behave this way. This is why I am thinking a second loop is required where if CurrentVendor = LastVendor, the second loop repeats until CurrentVendor < > LastVendor, then loop2 ends, the PO is created, and loop1 iterates to the next Vendor# and Warehouse.
The sedcond part of my question is regardless of one or two loops, how do I go about setting the values of CurrentVendor and LastVendor? I'm familiar with the Set Variable Value statement in the Keyword test, but not sure what the syntax for those variables should look like.
Thank you again for your help!
DC.
There's no reason a single pass through the loop won't work. Don't close the second screen until the Vendor # changes. Then open the first / second screen again and repeat.You could even leave the dept_name / vendor number blank and use this != null logic instead of tracking whether Vendor # changed. We store the one-to-many relationship as comma separated values to reduce the redundant data in the spreadsheet. This works best for a single value (i.e. item serial s1,s2,s3). There are places where multiple values are stored and use a second delinator i.e. (serial, quantity;serial, quantity). If your not a technical person the nested loops will be confusing.
Variables don't have a sytax - they are of a specific type (i.e. string, integer etc). Unless calculations are performed strings are fine - even if the value is a number.
Hi william_roe...
Thank you for the input. I'm not a technical person and this is all pretty new to me so please forgive my ignorance. I'm still muddling my way through all of this.
Humor me if you will, as I reiterate what I think you are suggesting - I'm probably going to get this worng but here it goes...
1) I replace any duplicate instance of Vendor# with NULL, or "" in my datasheet.
2) When Vendor# changes, I execute the portion of the test that creates the PO, and start the loop over with the next vendor.
Am I close?
If so, how do I tell the test that if the Vendor# changes to run the lines of the script that create the PO and restart the loop using the next vendor?
Thank you for your time.
DC.
DCat1223 wrote:Hi william_roe...
Thank you for the input. I'm not a technical person and this is all pretty new to me so please forgive my ignorance. I'm still muddling my way through all of this.
Humor me if you will, as I reiterate what I think you are suggesting - I'm probably going to get this worng but here it goes...
1) I replace any duplicate instance of Vendor# with NULL, or "" in my datasheet.
2) When Vendor# changes, I execute the portion of the test that creates the PO, and start the loop over with the next vendor.
Am I close?
If so, how do I tell the test that if the Vendor# changes to run the lines of the script that create the PO and restart the loop using the next vendor?
Thank you for your time.
DC.
1) Don't input "NULL' OR "" in the vend_num cell - simply delete the redundant value in the cells and in then perform an "if" operation where the value != null. (I can include a screen capture later if it would help)
2.) You don't need to start the loop over. Finish whatever needs to be done on page 2, the po detail (after the next non null vend_num value is found and return back to page 1 (the po header) and continue on to the next record in the loop.
Thank you william_roe. This was great. It took me a bit of trial and error and tinkering with the logic but this test script is now doing exactly what I was hoping it would do.
I really appreciate your patience and willingness to share your knowledge. This Smartbear User Community is outstanding and I have learned so much from all of you. There is still much to learn but one step at a time I guess.
Thanks again!
DC.