How can I copy a table?

This is very important for our company as well.  We have branches in several countries and often need to copy a table and rename by region.

We need the same thing as we have multiple projects with some variations. We are only just beginning to set up Quickbase and this is a do or die for our company. As Quickbase is not heavy on project management this is a feature that would really turn us off Quickbase altogether. Has this issue been resolved yet?

Wow, 2 years old and 3 years since a QuickBase reply; perhaps there are other threads but this one still comes up quick in searches and remains an issue.  The QB reply seems to indicate a "why don't you just do it our way" response yet there would appear to be many different reasons to want this functionality.

I also need different tables for different years.  Yes we could load this all into one table and differentiate with reports but when you have multiple reports, executive summaries and so forth the need to switch between them causes added complexity versus clicking on a table and seeing what you expect to find.  Simply needing to dictate the additional differentiation by stipulating the year when adding entries while dealing with multiple teams and participants invite far too much potential for error; inexcusable when dealing with millions of dollars in capital.  As simple as it may sound, in a turnover period between years this could easily cause trouble.  This is not to mention staffing changes or adding new or evolving metrics that were not tracked in previous iterations.

As for the reports themselves; while again being able to switch them to a different calendar year that is not ideal for all the above reasons so wanting them truly separate with the one table solution would require rebuilding all these reports.  Do yourselves a favor and do your own quick google search and count how many articles advise to copy the entire app then move the table, then rebuild a bunch of things that do not go with it.  Why is this still an issue?

Regards,
Scott

I agree with Scott and the rest of the comments above. I have had many instances where being able to copy the structure of a table within the same application would save me hours of work! It seems like such an easy feature to add (like copying a report or a field). I find myself finding "work arounds" in order to not have to copy an entire application. Usually these work arounds are not as efficient as just copying the table, however managing QB is not my full time job and I don't have the time/resources to play on it all day. I think there might be a disconnect with the QB design team and their users where they may assume we are all IT people. In most cases I have seen, the ones running their company's QB applications are like me (Engineers, General Managers, Executive Assistants, etc) and do not have a lot of extra time to modify their QB apps. Changes such as copying a table should be quick and painless in my opinion. The best part about QB for our company has been how much time it has saved us! It's all about efficiency here and this is just one spot where QB is falling short in my opinion.

Thanks for everyone's continued input on this.  as many of you may know we are in the process of designing the new QuickBase (code named Mercury) and these sorts of suggestions are vitally important to us.  Quick question... has everyone who has weighed in on this thread also added their votes in User Voice?  The suggestion is here: https://quickbase.uservoice.com/forums/111823-quickbase-product-feedback/suggestions/4008181-copy-tables-without-moving-to-another-app

I had an employee create a table in the wrong spot. I have numerous forms for one table and the form for that table needs to be with the rest. It was a tedious form to build thus I was looking for a way to move or copy the fields to a different table --- Sad Face :-(

I currently have an app with 73 tables that uses 1.4 GB of storage (and about 10 to 15 minutes of complete down time as the app is copied and nobody - all 74 users - can do anything while it copies). All I want to do is copy the table within the app so that I have a backup of everything in there before I have to delete all the records to test an identified bug (by support) that is in the connected table refresh mechanism and is preventing me from using the table at all. I don't want to export the table to Excel because that always loses information (I have a very large multi-line text field in there that can't be clipped to 256 characters).

So, you can see my dilemma. It is not good enough to tell us to clone the whole app, do a table rename in the cloned app, and then reimport the table. That will kill your server resources just as surely as our time. And, yes, I have voted on that suggestion. But it's a year later and still sitting there with 94 votes. While I greatly appreciate the User Voice mechanism for incorporating our feedback into your product development decisions, I get very frustrated with things like this. It's the biggest reason I left Salesforce after being on that platform for 7 years, as their continued platform development pales in comparison to yours.

What is you create a temporary app and absorb that table into that temp app.
Then make your copy of the temp app, and then absorb the table back into the main app.

But you also mentioned that it was a connected Sync table, so I'm not sure that will work.

I'm happy to announce that we released a new feature yesterday which lets an app admin copy a table directly, without the need to duplicate the entire app! For details, please see our release notes:

http://www.quickbase.com/quickbase-blog/september-2017-release-notes

Thx Brian,

Next we are hoping to see the ability to copy several tables which are in a relationship.  e.g. One Customer has Many Contacts.

We'd love the ability to copy both tables as a mini module to insert into a new app and have them maintain their relationship and lookup fields.  

That would also make the Exchange more useful as we could then grab a "module" (not sure what a set of tables in a relationship would be called) from one app and add that set of tables to an app that we are building.  Huge leverage opportunity there for that existing Exchange Library of 902 apps which have useful components which we'd love to carve out for our apps.

Keep those enhancements coming .....