Post

1 follower Follow
0
Avatar

Working without a shared project - Import/Export/Merge

Out of necessity I am in an environment where we are trialling CaseComplete and do not have the ability to create a Shared project. So we have individual trial copies, the work in which will ultimately (when the trial passes) be merged into one Project and then shared.

I have been experimenting with import and export functionality but to save time was wondering if there is any paper or hints on how to best manage this process.

The individuals are separated to a large extent by subject area, so I could defined a relatively separate directory structure etc.,

ANy help would be appreciated. A paper saying do this would be fabulous!

Thanks

Keith

Keith Matthews Answered

Please sign in to leave a comment.

1 comment

0
Avatar

 

There are a few things you can do to make sure this process will go smoother.

First, make sure the individuals working in their own projects are creating items with their own unique ID’s. This way, you won’t have ID conflicts when trying to import.

To do this, in their own projects, have each person create a package for the items that will eventually be imported. Right-click that package and select Save in Separate File. When prompted, select a Staring ID or prefix to make sure the items they create will have unique ID’s across all projects.

Second, when it comes time to import, select File / Import Package File and browse to the various packages that the individual team members created. This will pull their work into the main project.

Finally, once you’ve imported everything into your project, you could renumber the ID’s once more. Do this only if you want to get rid of the ID’s and/or prefixes that were used when creating items in the individual projects.

Following these few steps should help ensure the import process goes smoothly.

There are a few things you can do to make sure this process will go smoother.

First, make sure the individuals working in their own projects are creating items with their own unique ID’s. This way, you won’t have ID conflicts when trying to import. To do this, in their own projects, have each person create a package for the items that will eventually be imported. Right-click that package and select Save in Separate File. When prompted, select a Staring ID or prefix to make sure the items they create will have unique ID’s across all projects.

Second, when it comes time to import, select File / Import Package File and browse to the various packages that the individual team members created. This will pull their work into the main project.

Finally, once you’ve imported everything into your project, you could renumber the ID’s once more. Do this only if you want to get rid of the ID’s and/or prefixes that were used when creating items in the individual projects. To do this, select Tools / Renumber IDs in the main project.

Following these few steps should help ensure the import process goes smoothly.

Matt Terski 0 votes
Comment actions Permalink