The Admin Console allows you to migrate local cases to the CaseMap Server. During the import process, cases are converted in an Access database format to a SQL Server database format. It creates a brand new SQL case and copies all information from the old case into the new one. You will also have the option to create the new case on a specified server instead of using an existing one. CaseMap cases can be converted individually or bulk imported to the CaseMap Server. Duplicate cases will not be added to the list.
Once a case has been successfully imported to the CaseMap Server, the file extension on the local case is changed to ".001" to ensure that case staff can no longer open it in the client application. If a case already exists with the same name and extension, the numbers will increment to ".002" and ".003" to ensure a unique name.
You can also import a list of cases from a text file. The text file containing the list of cases must list one case per line. Each line must contain only the full path to the case file. The import utility will not add duplicate cases to the list.
When initiating the import process, you must use the administrative credentials you use in the SQL Server Properties dialog box in the CaseMap Admin Console. The CaseMap Administrative Credentials need to be filled in before you can import cases. This login must have the Create any database permissions on the specified SQL Server. This login will also become the database owner (dbo) for each imported CaseMap case.
Once the import process completes, a message box displays listing the number of cases successfully imported and any cases that failed to import. If you cancel the import during processing, CaseMap Server will finish importing the last case being processed before stopping.
After the case is imported, it's important to verify case users and assign them to roles in the CaseMap Admin Console. See About roles and users.
|
Once a case has been converted to a new version format, users can no longer access it using an older version of CaseMap. We recommend that all users get new versions installed at the same time.
|
| 1. | In the CaseMap Server pane, click SQL Cases. |
| 2. | On the Action menu, click Import Local Cases. |
| 3. | In the Import Local Cases dialog box, click CaseMap to select the type of case to import. |
| 4. | In the Which SQL case version do you want to create? list, select the CaseMap case version (e.g., CaseMap 12) for the files you want to import. |
|
You can only import any older version of local CaseMap cases at the same time. All cases imported will be converted to the selected CaseMap version.
|
| 5. | In the Which SQL Server should store the SQL cases? list, select the SQL Server you want to use. |
| 7. | In the Import Local CaseMap Cases dialog box, on the Case Selection tab, click Add Cases. |
| 8. | In the Select CaseMap Cases dialog box, navigate to the folder where your case files are stored. |
| 9. | Select the CaseMap case(s) you want to import and then click Open. |
| 10. | In the Import Local CaseMap Cases dialog box, review the case(s) selected for the import. |
To remove a case from the TextMap Access Cases to Import box, select the case you want to delete and click Remove.
| 11. | Click the Add from File button if you want to import a list of cases saved in a text file. |
In the message box to import a text file, click OK.
In the Select CaseMap Cases List, navigate to the file you want to import, then click Open.
| 12. | Click the Remove button to delete a case from the bulk import. |
| 13. | Click the Import button. |
| 14. | In the message box confirming the import, click OK. |
If you click Cancel during the Import process, the process will finish importing the last case before stopping.
| 15. | Click the Results tab to review each case that was processed. |
| 16. | To save a results log, click the Save Log button. |
| 17. | In the Save Import Log dialog box, navigate to the folder where you want to save the log file, then click Save. |
| 18. | Click the Clear button if you want to delete import results data. |
| 19. | On the File menu, click Exit when you are finished. |
|
