Validate required evidence types per dispute and resolve Drive file URLs. The workbook becomes the system of record; Apps Script owns the joins and business rules so analysts are not pasting monthly formulas.
Entry point `logDisputeEvidence` reads typed columns with SpreadsheetApp batch APIs. DriveApp is the primary service; onEdit describes how you usually invoke it after authorization.
Keep thresholds (grace days, bands, alert emails, API keys) in Config cells or Script Properties so the same .gs file promotes from sandbox to production without code edits.
This page is technical only: sheet layout, edge cases, runnable code, deploy steps, and FAQs for log dispute evidence completeness. No consulting pitch—just the pattern you can paste and harden.
Need this built? Hire a Google Apps Script developer →
Sheet / project setup
| Tab | Columns | Notes |
|---|---|---|
| Evidence | DisputeId, Type, DriveFileId, Uploaded, Url | Artifacts |
| EvidenceLog | Completeness | Output |
What this script does
logDisputeEvidence() validate required evidence types per dispute and resolve Drive file URLs.
- Required types
- Drive URLs
- COMPLETE flag
Prerequisites
Container-bound script on the workbook that contains the tabs in the setup table. Authorize DriveApp scopes on first run.
- V8 runtime
- Exact sheet names
- Script timezone = ops timezone
Walkthrough
Require POD+INVOICE+CHAT; resolve Drive URLs; summarize COMPLETE vs INCOMPLETE.
Paste the code, set Config/Properties, run logDisputeEvidence once, verify the output tab, then attach a onEdit trigger.
Edge cases
INVALID_ID in URL column means DriveApp could not open the file id—re-upload evidence.
Testing
Use a sandbox copy with 3–5 known rows. Compute expected outputs for log dispute evidence completeness offline, run logDisputeEvidence, and diff the output tab including one intentional bad row.
Hardening
Add LockService around multi-sheet writes if triggers can overlap. Log run timestamps. Keep API keys and alert emails in PropertiesService—not in shared cells.
Variations
Fork ideas: filter to one business unit, change grain (daily→weekly), or POST a summary payload after logDisputeEvidence succeeds.
Operations notes
Assign an owner for the output tab, document regenerate steps, and treat `logDisputeEvidence` as source of truth over ad-hoc cell formulas.
Full code: logDisputeEvidence()
Run logDisputeEvidence when source tabs are current. Edit sheet names and Config/Properties first.
function logDisputeEvidence(){
const ss=SpreadsheetApp.getActive();
const required=['POD','INVOICE','CHAT'];
const sh=ss.getSheetByName('Evidence');
const data=sh.getDataRange().getValues();
const byDispute={};
for(let i=1;i<data.length;i++){
const id=String(data[i][0]);
if(!byDispute[id]) byDispute[id]=new Set();
byDispute[id].add(String(data[i][1]).toUpperCase());
if(data[i][2]) {
try { data[i][4]=DriveApp.getFileById(String(data[i][2])).getUrl(); } catch(err){ data[i][4]='INVALID_ID'; }
}
}
const summary=Object.keys(byDispute).map(id=>{
const have=byDispute[id];
const missing=required.filter(t=>!have.has(t));
return [id, have.size, missing.join(','), missing.length? 'INCOMPLETE':'COMPLETE'];
});
sh.getRange(2,5,data.length,5).setValues(data.slice(1).map(r=>[r[4]||'']));
const out=ss.getSheetByName('EvidenceLog');
out.clearContents();
out.appendRow(['DisputeId','ArtifactCount','Missing','Status']);
if(summary.length) out.getRange(2,1,summary.length+1,4).setValues(summary);
}- Line 1: Entry point — bind triggers to logDisputeEvidence.
- Line 5: Batch read; avoid per-cell getValue in loops.
- Line 12: Drive file resolve/copy for artifacts.
- Line 20: Batch write output rows in one setValues call.
- Line 6: Rename sheet constants before production.
Deploy this example
- 01
Open Apps Script
In the bound spreadsheet: Extensions → Apps Script. For standalone projects, create one at script.google.com and link your Sheet by ID.
- 02
Paste and save
Add a .gs file, paste the code below, rename constants at the top (sheet names, column letters, API property keys), then save.
- 03
Authorize once
Run the main function from the editor. Accept OAuth scopes when prompted — triggers cannot run until authorization succeeds once.
- 04
Add the trigger
Triggers → Add trigger → choose the handler function and event (time-driven, on edit, or on form submit). Delete test triggers before production.
Before you run: log dispute evidence completeness
- 1Setup tabs exist with headers matching logDisputeEvidence
- 2Dry-run on a copy workbook
- 3Timezone verified
- 4DriveApp authorization completed
- 5Output spot-checked against hand calc
- 6onEdit trigger added only after validation
- 7Owners + alert recipients documented
Frequently asked questions
At minimum the tabs listed in the setup table for Log Dispute Evidence Completeness. Output tabs may be cleared each run—do not store source-of-truth data there.
Run from the Apps Script editor for dry runs. Production usually uses a onEdit trigger after OAuth succeeds once.
INVALID_ID in URL column means DriveApp could not open the file id—re-upload evidence.
Per-cell calls burn quota and wall time. One read + one write keeps this pattern under the 6-minute execution cap longer.
PropertiesService (Script Properties) for API keys and alert inboxes. Config sheet is fine for non-secret thresholds.
Simple ratios maybe; log dispute evidence completeness needs joins, branching, or side effects (email/Docs/API) that Apps Script handles cleanly.
Keep the .gs in clasp/git. Avoid divergent copies of formulas on the output tab—regenerate from the script.