Import issues due to locked Pre-built component file

Issue: Import Fails Due to Locked Pre-Built Library Import File

When importing pre-built component libraries into Opkey, you may encounter an issue where the import process fails because the library import file is locked. This typically occurs when the file has been used or modified in another Opkey environment, preventing it from being imported into your current environment.

Solution:

1. Request Admin Assistance:
   Contact your system administrator to unlock the file associated with the test cases before sharing the import file. Ensuring that the file is unlocked will allow the import process to proceed without any interruptions.

2. Use a Separate Opkey Environment for main library:
   To avoid potential locking issues, always export the pre-built library from a separate Opkey environment where the file has not been used or modified. By doing so, you can ensure that the file remains unlocked and ready for import into your desired environment.

3. Ensuring the destination folder is unlocked:
   
   
   
   Before importing the file, you should also ensure that the destination folder where you are importing the library is in unlocked state. You can contact your team admin to enquire whether a team member has locked any folder or not.

By following these steps, you can troubleshoot and resolve issues related to locked import files, ensuring a smooth import process for your pre-built component libraries in Opkey.