Delete a purchase-request attachment | Pixie CRM Help Centre Canonical: https://pixiecrm.com/help-centre/delete-a-purchase-request-attachment Publisher: Pixie Technologies LLC Purchase requests Delete a purchase-request attachment Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on. Remove a request file. Audience: Purchasing staff; Permission: purchase_request capability and status capability where applicable; Module v1.7.9; Where to goAdmin Area → Purchase → Purchase Request → open request → Files → Delete Before you start - Use an account with purchase_request capability and status capability where applicable 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 helps you do Remove a request file. The instructions reflect the supplied module’s registered menus, controller actions, views, settings and code-backed validation flow. Follow these steps - Go to Admin Area → Purchase → Purchase Request → open request → Files → Delete. - Go to the exact record and review linked documents, payments, approvals, files and portal visibility. - Select the supported Delete, Remove, Void or Cancel action. - Verify the action only after checking the consequence described below. - Return to the list and verify whether the record was removed, retained with a status, or blocked by a code-backed restriction. Fields and options Request headerRequest code/name, requester, type, department, project, related sales estimate/invoice, currency and rate. Request linesItems, description, quantity, unit, tax, price, discount, subtotal and total. SourcingSelected vendors, attachments, public share/request-for-quotation actions and approval status. Rules and limits - Purchase-request status changes use the dedicated purchase_request status capability in addition to record access. - Department can be mandatory when pur_department_required_condition is enabled. Check it worked - The supported delete a purchase-request 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. Related guides Download a purchase-request attachment (https://pixiecrm.com/help-centre/download-a-purchase-request-attachment)Copy a purchase request (https://pixiecrm.com/help-centre/copy-a-purchase-request)Create a purchase request (https://pixiecrm.com/help-centre/create-a-purchase-request)Create a purchase item (https://pixiecrm.com/help-centre/create-a-purchase-item)Create a purchase quotation (https://pixiecrm.com/help-centre/create-a-purchase-quotation)Browse all Purchase Management guides (https://pixiecrm.com/help-centre/category/purchase-management)Expenses Finance (https://pixiecrm.com/help-centre/category/expenses-finance)Invoices Payments (https://pixiecrm.com/help-centre/category/invoices-payments)Contracts Documents (https://pixiecrm.com/help-centre/category/contracts-documents)