Attendly Vault

2026-01-19 - AR Codes Configuration for Reporting

1 min read

2026-01-19: AR Codes Configuration for Multi-District Reporting

For: SJCA, SAUSD, Romoland Impact: Enables dynamic AR code filtering in reports, eliminating hard-coded attendance reason codes and allowing per-district customization Context: Attendance reporting currently has AR codes hard-coded. Adding reportingParameters.ARCodes to organization metadata allows reports to pull valid codes dynamically per tenant.

Implementation: Added reportingParameters.ARCodes array to organization.metadata JSONB field for three districts:

DistrictAR Codes
SJCAA, E, H, K, N, P, S, U, V, W, X, Z
SAUSDD, H, I, J, M, T, U, X
Romoland2, 6, 7, A, E, P, Q, S, U, W, X

SAUSD already had reportingParameters.ASSIST configured; ARCodes was added alongside using jsonb_set() to preserve existing keys.

SQL Pattern Used:

-- For new reportingParameters (SJCA, Romoland):
UPDATE organization
SET metadata = COALESCE(metadata, '{}'::jsonb) || 
    '{"reportingParameters": {"ARCodes": [...]}}'::jsonb
WHERE name = 'DistrictName';
 
-- For existing reportingParameters (SAUSD):
UPDATE organization
SET metadata = jsonb_set(
    metadata,
    '{reportingParameters,ARCodes}',
    '[...]'::jsonb
)
WHERE name = 'SAUSD';

Related: Admin Reporting Interface, Hub

Graph View