Upload a purchase item attachment
Attach a file to an item.
Exact navigationAdmin Area → Purchase → Items → open item → Files → Upload
Before you begin
- Use an account with purchase_items or purchase_vendor_items capability and confirm the intended record or setting before making a change.
- Follow the exact route above. If the screen or action is absent, check module activation, ownership and permissions rather than using another person’s account.
- Use controlled test data for configuration, integration, email, AI, payment, portal or automation changes before production-wide use.
What this guide covers
Attach a file to an item. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow.
Exact step-by-step process
- Open Admin Area → Purchase → Items → open item → Files → Upload.
- Download or inspect the supported template/field requirements before preparing the file.
- Choose the Import or Upload action and select the intended file only.
- Run validation and correct rejected rows, file types or required values.
- Complete the import/upload and review the created records, attachments and any error file.
Fields, choices and supported possibilities
Item masterCommodity/item code, description, group/subgroup, unit, purchase price, tax and purchase eligibility.
Vendor-item mappingVendor, group and selected item list, shared visibility and vendor-specific values where exposed.
Files/importAttachments, spreadsheet import rows, validation errors and generated barcode/code.
Code-backed validations and workflow rules
- Item and vendor-item operations use separate capability groups.
- Spreadsheet imports can create an error file for rejected rows; review it before retrying.
Expected result and verification
- The supported upload a purchase item attachment flow completes without bypassing permission or validation checks.
- The resulting record, setting, status, file, delivery event or external response is visible from the relevant workspace.
- Unexpected validation, provider or linked-record errors are investigated before retrying.
Security, privacy and operational checks
- Apply least privilege to purchasing, vendor, invoice, payment, return, contract and report permissions.
- Verify vendor identity, bank/payment details, tax, currency, totals and approvals before creating financial commitments.
- Treat public links, signatures, portal files, attachments and exported reports as controlled business records.
- Test settings and automated jobs with controlled records before production-wide use.