Forum Discussion
I would export it to Excel from the one project suite and then use these script examples to build the table in the other suite.
Thanks for the response.
I tried that. Got it to export to excel just fine, but when I tried to build the table variable, it put the values in the temporary portion of the table, didn't set the defaults. I couldn't figure out how to set the defaults, which meant I would need to either use a persistent variable (and it would have been the only one in the project -- I don't like exceptions.) or I'd need to re-fill it from the excel file each run.
This is what I was doing a while back, and I found external data storages to be unreliable and hard to work with.
What I ended up doing was rewriting the little subroutine I had made that exports it to the text file so that it would save a column of values instead of a comma delimited string.
Then I used the data generator's 'values from a set' to import the values from the text file one column at a time.
Clunky and roundabout, or what I like to call sledge-hammer programming.
Figuring it out probably took about as long as re-typing the whole table would have.
But I finally had the default values set in the new project suite variable, like I wanted, without having to re-enter all the data.
And now I know how to move a variable between suites, in case I ever need to do it again.