You can reopen a closed file when a matter needs more work, billing, or corrections. This article explains how to find a closed file, reopen it, and fix common errors. Use it when you can't find your closed files, Reopen is unavailable, or you see an "Invalid area of law", "Database error", or field-length error when reopening.
Finding a Closed File
To do this:
- Go to Reports > Contact > Closed Files.
- Press Ctrl+F and search for the file number.
Reopening a File
To do this:
- Go to Contacts > File Manager.
- Click Reopen A File (bottom right).
- Search for the closed file. Its number may end in *1.
- Select the file.
- Click Reopen.
If the reopened file number ends in *1, see Removing the *1 Suffix from a Reopened File.
Fixing Errors When Reopening a File
Reopen Is Unavailable
Possible cause: The client contact is closed.
To fix this:
- Go to Contacts > Contact Manager > Reopen A Contact.
- Search for the contact.
- Click the circled arrow (▶).
- Click Reopen.
- Reopen the file.
'Unable to Reopen File. Error: Invalid Area of Law' Error
Possible cause: The file's area of practice is missing or no longer active. This often happens with files that were closed in your previous software before you moved to Legal Accounting.
- If the area of practice was deleted or deactivated, have an admin set it up again under Administrator Settings > Firm > Areas of Practice, and then reopen the file.
- If the file never had an area of practice (for example, it was migrated), or reactivating doesn't help, contact Actionstep Support. Closed files can't be edited. Include your license number, each file number (with *1), and the area of practice each file should have.
'Database Error' with NetDocuments Connected
To fix this:
- Disable NetDocuments.
- Reopen the file.
- Reconnect NetDocuments.
'Length Cannot Exceed the Maximum Width Specified in Setting Up Field' Error
Possible cause: A field on the closed file is too long, and closed files can't be edited.
- Contact Actionstep Support. Include your license number, the file number (with *1), and the error.
Additional Resources:
Updated