Bulk Import Locks with CSV File

If you own a large number of locks and prefer to bind them in bulk rather than one at a time, you can easily accomplish this using a CSV file. This guide will walk you through the steps to bulk-import locks into your locking system.

Preparing the CSV File

To create a CSV file, use Excel or any similar spreadsheet software. Enter your data, organize it using headers for each column, and then save the file in the .csv format. This ensures compatibility with other software.

To ensure a successful import, your CSV file must include the following columns:

• Title: This field specifies the name of the lock as it appears in the Tapkey locking system.
• Description: A text that provides additional details to help you identify the lock within the system.
• BindingCode: The registration code of the specific lock.
• PhysicalLockIdB64 or PhysicalLockIdHex: The ID of the physical lock to be bound to the locking system, provided in either Base64 or hexadecimal format. Only one of these values is allowed to be used.

Example:

title;description;bindingCode;physicalLockIdHex
Office Entrance;Main door;12345;1A2B3C4D
Meeting Room A12;First floor;54321,1A2A3A4A

 or 

title;description;bindingCode;physicalLockIdB64
Office Entrance;Main door;12345;UGk2sg==
Meeting Room A12;1st floor;54321,iEEalg==

Steps to Bulk Import Locks

1. Navigate to the Locks section: 
   • After logging into your Locking System, go to the Locks section. Here, you will find the BULK IMPORT option.
2. Upload the CSV File:
   • Click on Choose File to select the CSV file you’ve prepared. Once selected, proceed to upload the file.
3. Completion:
   • After the import process is complete, you will receive a confirmation. The successfully imported locks will now appear in your locks list, along with their corresponding titles and descriptions.

Troubleshooting

• Registration code missing: Ensure that the BindingCode field is not left empty.
  Lock ID is missing: At least one of the lock ID fields must be defined, either PhysicalLockIdB64 or PhysicalLockIdHex.
• Multiple IDs defined: Only one ID field should be defined—either PhysicalLockIdB64 or PhysicalLockIdHex - not both.
• Lock ID has incorrect format: The lock ID does not match the expected format. If using PhysicalLockIdB64, it should be a Base64-encoded string. If using PhysicalLockIdHex, it must be in hexadecimal format.
• Lock already bound: The physical lock is already bound to a different locking system.

By following these steps, you can quickly import locks in bulk and effectively manage their access.