Move a variable between two project suites

Question

I have two project suites.One of the project suites has a rather large table variable that I use as a lookup for specific x/y values to be clicked during a test.I'd like to duplicate the default values for this table in the other suite.Is there some way to export a table variable's contents, and then import it into another suite?&nbsp;I did manage to produce a comma delimited text file from my original table, but when I try to fill the empty table with that, it wants to put all the data into the first cell.&nbsp;I can use the split method in a script to make a temporary table full of &nbsp;the values, but don't know any scripting way of setting the default values in my target table...&nbsp;I'm beating my head against the wall, here, trying to move this stupid table without re-entering all the data.&nbsp;Any suggestions?

marsha_r · Answer

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.&nbsp;http://support.smartbear.com/viewarticle/55435

joe_2 · Answer

Thanks for the response.&nbsp;I tried that. &nbsp;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. &nbsp;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.&nbsp;This is what I was doing a while back,&nbsp;and I found external data storages to be unreliable and hard to work with.&nbsp;What I ended up doing was rewriting the little subroutine I had made that exports it to the&nbsp;text file&nbsp;so that it would save a column of values instead of a comma delimited string. &nbsp;Then I used the data generator's 'values from a set' to import the values from the text file one column at a time.&nbsp;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.&nbsp;

marsha_r · Answer

You might consider putting the data in an external file instead of a variable. &nbsp;Then you could just copy it around wherever you need it.

joe_2 · Answer

Yeah, when I was first learning how to use TestComplete, I made heavy use of external data storages.But I found they were somewhat unreliable. &nbsp;Occasionally a test would fail for inability to open a file, for one reason or another.Usually because the file in question had been moved by someone else...So I did away with them in my projects. &nbsp;Just use table variables now, and that's generally not a problem, except I started a new suite and needed a few of the old tables in it.&nbsp;What I wish is that SmartBear would make the project variables and suite variables copy&nbsp;and paste-able.Just right click a suite variable and copy it, then paste it into the other suite.&nbsp;Now I'd find that useful.

Forum Discussion

Move a variable between two project suites

Related Content

Using project/context/testRunner variables

Project Suite Variables for Individual Workstations

how to run jenkins job same project with different environment variable

Sample project

Persistent ProjectSuite variables??

Recent Discussions

Onscreen Object Selector Slowness

aqObject.CheckProperty() slowness

Problem with generated data table and keyword test

WebView2 support does not work

System checks for Object for every test