Import Errors
Import validation checks the spreadsheet before saving records.
Common import errors include:
- Missing required email.
- Duplicate email.
- Invalid member type code.
- Invalid membership plan code.
- Invalid date format.
- Unmatched library name.
- Unsupported image file.
Dates must match the organization date format shown in the import screen.
Do And Don'ts
- Use the sample template generated by the software.
- Validate the file and review row-level errors before import.
- Keep dates in the organization date format and let the software store them internally.
- Don't rename required headers to unsupported wording.
- Don't import large files without testing a small sample first.
- Don't ignore duplicate email, phone, Member ID, staff ID, role, plan, or library errors.
FAQ
Who should read this page?
Admins and staff should read this page when they need to understand or complete the Import Errors workflow in Libcodesk.
Does this work in both Libcodesk WebApp and Standalone app?
When a workflow differs between Libcodesk WebApp and the Standalone app, the guide points out the setup-specific step so staff can follow the right path.
Does local setup use the same steps?
Local setup follows the same user workflow where the feature exists, but the work stays on the Standalone app device instead of Cloud setup.
What permission do I need?
If you cannot see the menu or action, your staff role probably does not include the required permission. Ask your organization admin to review your role.
Why is the Save button disabled?
Save and update buttons stay disabled until Libcodesk detects a real change. This prevents accidental writes, unnecessary logs, and duplicate requests.
How do I fix validation errors?
Read the message beside the active button or inside the modal. Required fields, duplicate values, invalid dates, and permission issues must be corrected before saving.
Can I use imports instead of manual entry?
Where import is available, it is recommended for larger datasets. Always validate the file first and review row-level errors before importing.
Where should staff or members ask for help?
Staff should contact their organization admin. Members should contact their library. Organization admins may contact CodeAchi for license, billing, or cloud access issues.