Documentation Index
Fetch the complete documentation index at: https://docs.younegotiate.com/llms.txt
Use this file to discover all available pages before exploring further.
Real-World Example
Maya receives a CSV of 800 creditor prospects. She uploads it in Import Creditor Profiles. The portal checks the headers first, shows which required headers are present, stores the file, creates upload history, and queues the import. If 780 rows are valid and 20 rows have duplicate or invalid data, the valid profiles should still be created and the failed rows should be available in a failed CSV.Visual Flow
Required CSV Fields
The upload expects the creditor profile headers defined by the app, including company name, address, city, state, zip, phone, URL, company email, and optional contact fields for up to three contacts.How It Should Work
- It should accept CSV uploads only.
- It should normalize headers and detect required headers before submitting.
- It should store the uploaded file and create an import history record.
- It should process rows in a queued job, not inside the browser request.
- It should create contacts only when contact first and last name are present.
How It Should Not Work
- It should not import files with missing required headers.
- It should not create duplicate profiles for the same company name, city, and state.
- It should not stop the entire import because one row is invalid.
- It should not create creditor consumer accounts; this import is only for creditor profiles.
Developer Notes
- Import history starts as
Queued, moves toIn-Progress, then becomesCompletedorFailed. - Failed rows are written to a failed CSV with an
Errorscolumn. - The job runs on the
importsqueue.
Related App Areas
app/Livewire/ConsumerResponseManager/ImportCreditorProfiles/IndexPage.phpapp/Livewire/ConsumerResponseManager/Forms/ImportCreditorProfiles/IndexForm.phpapp/Jobs/ImportCreditorProfilesJob.phpapp/Enums/CreditorProfileFields.php

