Hi Winicjusz,
Thanks for the response. I believe, the compare matrix scenario will work only if the matrix values are the same while recording and playing back. How can we handle a situation when the expected values in the matrix are dynamic and different than the recorded values?
Let me explain the scenario once again.
The Payment Term combo in our add-on Payment Term Search form will list the payment terms ZPNET30, NET30, -Cash Basic’ etc. On selecting one of these values (say NET30), the matrix in the form is expected to list only those BPs with matching payment term(NET30). I need to ensure that all the BPs listed here are having the same payment term ‘NET30’. When I rerun the script the BPs list might vary because of addition of new BPs to the database or change in the payment term value of the existing BPs.
When I manually do the testing, I apply the filter and then load each of the BP Master Data to check whether the payment term matches the selected one in the search form. Then I will change and update the payment term of the existing BP or add new BPs and again performs the filtering to check whether the search result is correct. Is there a mechanism with B1 TC to handle such scenario? Like accessing each individual rows/cells of the matrix/grid.