R
RichardWalsh
Guest
Hello Santosh Thanks for your reply. Relationships, as you say, get exported as part of the Application XML. (and seed records where required) This is fine when you begin a new instance of an application in a different tenant (in this case my development account), As you build new records that 'belong' to each other the appropriate relationships will be created by Rollbase. However it does not seem to be possible to export the data , say as spreadsheets, and then import them together with the relationships they had in the original Rollbase database. If we take an example of a Property Table and a Tenant table. In the original database it might show the property assigned to a tenant and vice-versa. It appears that I cannot export this relationship along with the data and the result in my new Rollbase instance is a series of tables/objects accurately relflecting the data in the original tables but without any relationships with records in any other table. Am I missing something ? If not how might someone move from private cloud to public cloud or vice-versa ? My main concern is that the client should be able to backup for himself/herself everything that would be needed to rebuild a Rollbase database in the event of a catastrophe, whatever the reason. Thanks Richard From: "Santosh Patel" bounce-sapatel@community.progress.com To: "TU Rollbase" TU.Rollbase@community.progress.com Sent: Tuesday, 29 April, 2014 6:29:53 PM Subject: RE: Transfer all data and structure from one Rollbase online account to another RE: Transfer all data and structure from one Rollbase online account to another Reply by Santosh Patel Richard, Rollbase uses unique IDs that are unique across records, object definition, field definitions and many such entities. Backing up data from one tenant (including these unique IDs) and restoring to another tenant would involve all entities to have new unique IDs. The IDs are unique across a Rollbase instance. This is why our backup/restore functionality for Private Cloud recommends that you start with a fresh Database so that no IDs conflict. As of today the viable option you are looking for is Seed records. Check out documentation.progress.com/.../index.html Basically you attach certain records as seed for any application. When you export application the seed records are part of the application XML and are available when the application is installed on another tenant. Also, relationships do get exported as part of the application XML. Please verify again and revert on this. Do get back with questions if any? Regards, Santosh Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...