FrequentlyAsked Question / Exact Problem
- “I uploaded customers but they are not visible in the system.”
- “Getting an error when doing a customer upload for Pepe Jeans.”
- “Lead upload via UI is not working.”
- “Product upload for PN Rao is stuck — still showing ‘In Progress’.”
- “E-Comm bill upload failed — date format issue.”
Affected Tenant / Context
Pepe Jeans (customer + product + bill upload), iPlanet (lead upload via UI), PN Rao (product
upload), Mufti (E-Comm upload with date format issue), Kidza (customer upload error), general.
Root Cause
- Incorrect date format in upload file — Mufti’s E-Commerce upload used MM/DD/YYYY
(US format) instead of DD/MM/YYYY. This caused bills to be recorded with future dates
(e.g., Sept 3rd instead of March 9th). The system accepted them without validation. - Custom field / column mismatch in lead upload template — iPlanet’s lead upload file
included custom fields (Persona, Time Slot) that weren’t in the default template. The
upload reader service ( WalkInInterestReaderService ) didn’t support those fields. - Missing product hierarchy columns in CSV — A lead upload file contained a column
named Doors as a product field name. CASA expected specific product hierarchy column names (e.g., bills_products_productInfo_Category ). The column was not recognized, causing the upload to fail with: Exception: Missing columns:
‘bills_products_productInfo_Doors’ . - Upload stuck in queue — Some product uploads remain in “In Progress” state if the Kafka consumer is backlogged or if there’s a schema mismatch that causes silent failure.
- Tenant muffler enabled — For Pepe Jeans, the “muffler” (test mode) was enabled,
preventing actual SMS delivery for test uploads. Not a failure per se, but often mistaken for one.
Common Debugging Steps (For CS Team)
- Download the error file from the upload results screen — it will show which rows failed
and the exact reason. - For date-related issues: open the CSV in a text editor (not Excel — Excel auto-reformats
dates) and verify the date column format. - For lead upload: ensure the CSV template matches the latest template downloaded from
CASA. Do not add custom column names. - For product fields in lead upload: the column name must match the exact product hierarchy field name configured in CASA, not free text like “Doors” or “Furniture.”
- If the upload shows “In Progress” for more than 30 minutes: tag dev with the Upload Job ID (visible in upload history screen).
- Check if muffler is enabled (test mode) — visible in tenant settings
Fix Made & Developer Conclusion
- Mufti date format: Upload deleted and corrected file uploaded. Future dates now flagged.
- Enhancement: validate date format before upload and add future-date guard.
iPlanet lead upload with Persona/Time Slot: Code fix to WalkInInterestReaderService
to support the new fields. Until fix was live, leads were uploaded manually by dev. - Missing column error: CS team coached on correct product hierarchy field names.
Documented field mapping shared. - Upload stuck: Kafka consumer issue resolved. Upload logs checked by dev using job ID.
Exact Dev to Reach Out To
Vishnuj — Bill/E-Comm upload pipeline, date validation
Dineshr — Lead upload, queue management
Rishvanth K S — iPlanet lead upload, custom field configuration
Shriram — Product upload, store master upload, column mapping