Duplicating a solution

Classic Servoy
1

I would like to duplicate the CRM example solution and use that as a starting point for a new solution, but I can’t make it work. I’ve tried “Import Clean”, but that forces me to duplicate style sheets and modules, which I don’t want to do - I want the new solution to reside in the repository next to the other solutions and use the existing styles & modules. If I “skip” the style & module dialogs, the new solution does not work. There must be a simple way to do this…

Thanks
Bill

2

Hi Bill

this post should cover what you need

hope this helps

3

Thanks, I saw that post when looking for answers. Unfortunately it doesn’t give me any new information.

I still can’t duplicate a solution without duplicating all the styles and modules as well. I don’t want to duplicate anything but the main solution.

Bill

4

Are you working on Mac or on Windows computer ?

DomTom.

5

Working on a Mac.

Here’s what happens: When I do a “clean import” of the servoy_sample_crm.servoy file, skipping the renaming of styles and modules, I get what looks like a new solution based on the old one. But it doesn’t work correctly. Elements are missing from the interface, and it takes almost 10 minutes to open the new solution (vs 30-60 seconds to open the original crm solution).

I even tried exporting the original crm and then reimporting (clean), but I get the same results.

6

Hi Bill,

This is because of the very nature of using modules.
The main solution uses a core module that contains the image media and some general purpose methods that in turn are used in the main solution.
So when you copy only the main solution you end up with loose ends.

7

You will find annexed a small procedure I use to do it.

DomTom

MacCreateDbConn&ImportSolution.doc (5.13 KB)

MacCreateDbConn&ImportSolution.doc (5.13 KB)

8

Thanks all for the feedback.

Roclasi wrote:

So when you copy only the main solution you end up with loose ends.

But the solution I’m copying still has the servoy core module referenced in the modules list, even after the clean import skipping style/module renaming. And isn’t that the whole point of modules - so you can reuse a single module for multiple solutions? Maybe I’m misunderstanding modules.

Thanks Domtom for the instructions. I’m shocked that this is what is reqired to duplicate a solution.

I’m finding project management to be the weakest part of Servoy. Duplicating solutions, moving solutions, switiching solutions, multiple developers, repointing db connections - these are all things that are a major PITA with Servoy. Coming from Filemaker, I thought the actual development would be the hard part. But I get that - tab panels, sql, javascript - no problem. What I find to be incredibly clumsy is having to wrestle Servoy so that my consultancy can easily get new customers’ projects started and integrated on our servers, using components and “starters” from previous projects.

With Filemaker it’s a no-brainer: Copy the main solution file, rename it, open it with server, done. Even with our web/php projects, it’s as simple as duplicating a folder.

I would love to see the Servoy repository window fleshed out into a project management tool, allowing us to easily duplicate & move solutions, define & repoint db connections, and define module references. And somewhere there should be an interface for definining a list of regularly used repositories with the ability to quickly switch from one to another. Also nice would be the ability to copy a solution from one repository directly to another.

If I’m wrong about any of this and missing something vital, I would love to be enlightened.

wbr