* Can one duplicate and rename a Repository?

[Gary_G]

I'm setting up repositories in new project and some repositories have similar content to the extent that it would be very handy to be able to duplicate them and change the relevant details. I've looked in the Forums, the Knowledge Base and the Help files, as well as trying various things on a test database. I can't see any easy way to do this. Has anyone any suggestions short of creating each from scratch?

[AdrianBruce]

The PlugIn "Clone Any Record" appears to work on Repositories as well as other records. I haven't checked all possible things that hang off Repositories though...

[Gary_G]

Thanks, Adrian.

In this case, I'm preparing to start a "REDO" of my database. The Repositories are not yet connected to anything, so If the plug-in can clone Repositories it should work fine. I wasn't aware that it considered a Repository to be just another record. I'll give it a try and post to say how it went.

[Gary_G]

Adrian;

Thank you. Your suggestion worked perfectly!

[tatewise]

Gary, in the Records Window there are 12 tabs and each one holds a type of Record.

[AdrianBruce]

Gary, in the Records Window there are 12 tabs and each one holds a type of Record.

I had to have a look down one particular rabbit hole - for no good reason other than to see what happened ....

It was a little "interesting" to clone a Source Template Record, with a new Name, of course. Its Name seemingly has to match a Source Template Definition - the Compare / Sync can be made to look at the cloned ST Record with the altered name but the changed name can only be synched from the ST Definition to the ST Record. At least, I think that's so ... being a generic source user, I could be missing lots.

As I said, I had no good reason to do this other than curiosity.

[tatewise]

Adrian, you would have to use the plugin that copies Source Template Records to the Source Template Definitions to in effect sync them together.

[AdrianBruce]

Adrian, you would have to use the plugin that copies Source Template Records to the Source Template Definitions to in effect sync them together.

OK - I'd forgotten about that one, thanks. But as I say, I could think of no good reason to clone an ST Record - in my (generic) head, working from the ST Definitions seems far better. One can clone an STD and the tools for working with ST Definitions make things more visible, IIRC.

There may be a good reason to clone an ST Record - but I don't know what it is - I was just shaking the tree to see what happened. Still, nice to know there's one way out.