History and reconciliation only. Not a live workflow.
Status: historical context, not an active user workflow.
The current application reads and writes the BizDB-backed Laravel system. Legacy AppSheet identifiers and imported operational fields remain where needed for history and reconciliation.
The earlier three-phase backfill, dual-write and cutover plan is superseded as a current build instruction. No active AppSheet dual-write path and no U Money daily-pull replacement is evidenced in this repository.
Encik Beku moved onto the new module on Wednesday 20 August 2026.
| Data | Volume |
|---|---|
| Job logs | ~11,000, marked imported |
| Refund rows | 58 |
| Historical order log | ~15,600 rows × 27 columns, retained for migration and reconciliation reference |
| Johor running number | Continues from JSM0170 → module starts at JSM0171 |
Story. As the system, I want any future legacy import to be idempotent and provenance-rich, so that reruns do not duplicate operational records.
Acceptance. Imported rows retain original reference, source, import run, mapping result and reconciliation status.
Story. As Operations, I want legacy records searchable for reconciliation without making AppSheet the live source, so that historical questions can be answered safely.
Acceptance. New operational changes are written only to the current system unless a separately approved migration run is active.
The weekly sales dashboard lost its data feed. Order count, sales quoted by Indoor and sales verified by Account were being pulled out of AppSheet.
Recommendation: a read-only endpoint or view returning those two numbers for a date range. Q12.
New to these terms? See the Glossary.