With the asset assignments import, you can assign assets that already exist in PeopleForce to employees and update their assignment details without editing each asset manually.
🧾 Prepare your file
Download the template to your computer and use it as a reference. (This sample is for reference only.)
Complete the following fields:
asset_code (mandatory): the code of an existing asset.
employee (mandatory): the email address or ID of an employee.
💡 Use the same employee identifier type throughout the entire file: email addresses or internal IDs. Do not mix different identifier types within one import.
issued_on (mandatory): the date when the asset was issued to the employee.
returned_on: the date when the employee returned the asset. Leave this field blank if the employee still holds the asset.
How existing assignments are updated
PeopleForce identifies an existing assignment by the combination of the asset code and employee:
If the asset is not assigned to that employee, a new assignment is created.
If an assignment with the same asset code and employee already exists, its issue and return dates are updated instead of creating a duplicate.
To transfer an asset between employees, include one row with the return date for the previous employee and another row with the issue date for the new employee.
📤 Import asset assignments into the system
Go to Settings > Imports.
Select Assign asset as the import type.
Upload your completed file.
Check the field mapping. The system maps matching columns automatically where possible. Manually map any fields that were not recognised.
Click Next to preview the data.
Review the preview and start the import. Valid rows are processed even if other rows contain errors. Invalid rows are skipped and recorded in the import results.
✅ The system validates each row automatically. Cells containing invalid data are highlighted in red. Correct them in your file and import it again.
📊 Track file upload history
Open Import history to view your imports.
Check the numbers of imported and updated records and any errors encountered.
Open an import entry to view detailed error messages.
