Workflow

How to Edit and Remove CRM Lead Values

Verified end to end. A disposable CRM lead list was created from a two-row CSV, one imported value row was edited inline, another row was removed with the selected-row bulk action, the remaining row and record count were verified, and the lead list was deleted after cleanup.

Evidence Summary

Workflow run
crm-lead-values-edit-delete-20260520T012503Z
Lead id
22
Edited value row
id=1, field nome
Deleted value row
id=2
Final lead-list records
1
Final state
Lead list deleted and absent from DT_SelectLeads

Edit an Imported Lead Row

  1. Open /crm/leads.
  2. Open the lead list detail page.
  3. In the Lead List tab, click an editable imported-value cell such as name, email, locality, address, country, mobile phone, or taxpayer number.
  4. Enter the new value inline and leave the field to submit the edit.

The verified edit changed imported row 1 from AI Lead Row One 20260520T012503Z to AI Lead Row Edited 20260520T012503Z. The request posted action=leads, option=updateLeadColumnValue, id=1, id_lead=22, field=nome, and value=AI Lead Row Edited 20260520T012503Z. OfficeGest returned bare JSON true.

Remove Selected Imported Rows

  1. Select one or more imported rows in the lead-list table.
  2. Open With selected.
  3. Choose Remove.
  4. Confirm the removal prompt.

The verified removal used the bulk endpoint leads / innerLeadsDelete with ids=2 and lead=22. OfficeGest returned bare JSON true. The next DT_Select_Leads lookup returned only row 1 with the edited name, and DT_SelectLeads returned lead-list row 22 with records=1.

The detail page also exposes a row trash icon that calls leads / innerLeadDelete for one row. This run verified the selected-row bulk remove path.

Column Map Context

The same detail page contains a Column Map tab. Its selectors map OfficeGest target fields such as nome, email, localidade, morada, pais, telemovel, and ncontrib to imported source columns. On change, the page calls leads / getLeadColumnSingularity with id_lead, column_orig, and column_dest to prevent duplicate or invalid mappings.

This run did not change column mappings because the imported CSV already matched the expected fields. Use the map before converting leads to prospects or adding them to communications when the CSV columns do not match the expected OfficeGest fields.

Artifacts