Hi,
I need to copy an existing application with cdt and data source in the same server environment with a different application name. Kindly let me know the best practice for this and the easiest way of doing this. I also need to create a copy of the table structures used in the DB.
Thanks in advance,
Swetha.
Discussion posts and replies are publicly visible
There is no best practice as there is no supported way of doing this.
It might be useful to clarify that you mean there's no automated way of doing it - but I'd suggest that at least there *is* a "supported" way of doing it, which is "the manual way", which (depending on the size of the original application) would most likely be long and painful. But if it were (for the sake of argument) just a demo app with 2 forms and 1 table with 1 CDT, then it could be banged out in maybe 10 minutes.
A more interesting question would be why you even want to do this? What's the purpose of you being able to clone an existing app?
Hi Stewart,
The client needs this. One copy for their internal use and one for their vendor.
One-by-one. Manually!!!
Why not have both client and vendor share the same app, and keep the two communities partitioned using Groups?
Hi Stewart, They will point to the same db tables and records. It will cause a mix up of data. If we differentiate them with groups, I will have to put a check in every object for the group again.
If you have to put a check in every object then your app isn't the same app!!! Can you not partition the data by tagging each data item? Then you only need to check which group they're in in the default filter when reading from the database tables
Depending on your compliance requirements it might not be allowed to put data of multiple client into the same tables.
If this is OK, then it is pretty simple to separate groups in applications. It only becomes a problem when one group wants a specific customization.
If putting the data in different tables is a requirement you could create a separation at the Data layer (have different Datastores pointing at different Database Schemas, and likewise with the Records) but this brings with it a maintenance overhead, although less than separating into two copies of the entire stack!