Projects
Discovered two issues after yesterday's Cash Movement Report frontend deploy. First, the amount column displays absolute values instead of net values. This stems from a discrepancy between environments: dev data uses positive amounts for all cash movements, while production uses negative amounts for outflows. Second, sorting by any column returns a 500 error from the API because the frontend sort parameter names don't match what the backend expects.