I’m facing a situation where cloning an application is not copying the database entries. Is there some constraint on this or change in behavior - I tried cloning into a new account as well and still the database entries are not copied.
Is there some way to make a database copy, i.e., a snapshot, before some major processing is run on the data?
I cloned a few apps yesterday, and all the tables were duplicated.
I would love to be able to specify what to do with the tables. Here is an old FR: Select branch and data for clone link
Several ways. Search the Forum for “table backup”.
I’m getting the same problem: cloning an app does duplicate the tables, but does not populate them with duplicated data.
Hi @stefano.menci,
Just to check, has the app still not cloned over the data? If there is a lot of data that needs to be copied over, the app will successfully clone before it has finished adding the data.
If not, can you send over a clone link or an app ID for me to look into?
Hi Brooke,
You’re right, the issue turned out to be the size of the tables.
This app (like most of mine) shares a Log table from a Logger app, and that table contains roughly 200,000 recent log rows. When I first cloned the app, I checked the tables and saw no data, so I assumed the clone had failed and deleted it, then continued working.
I checked again now and the clone was actually still present, with the table data correctly duplicated. It looks like the app deletion didn’t complete because the table data cloning was still in progress.
This ties back to the FR I mentioned in my previous post: in cases like this, it would be very useful to be able to control table behavior during cloning, for example, choosing which tables should duplicate data, which should be shared (when cloning within the same account), and which should be created empty.