Development Database

Good morning,

Is there a way, of having a duplicate database of which development changes can occur and be tested before transferring to the live system?


If your database is on-live now, generally we would suggest manual backup before you make any major design changes.

A workaround would be as below:

Step 1. Register another Ragic database for developing purposes.

Step 2. Backup your live account and restore it to the developing account.
*Note: you can suspend all other users in the developing account if you don’t want to let others have the access right to access it.

Step 3. Modify the sheet design in the developing account and test to see if the new design works perfectly.

Step 4. Backup the database definition of the developing account and then restore it to the live account.
Note: the database definition means the structure and sheet design of the database, excluding entries.