Backlog
Under consideration
No Backlog issues
Next up
Committed and queued
No Next up issues
In Progress
Actively being built
No In Progress issues
Fix to be Verified
Actively being built
No Fix to be Verified issues
Done
11Recently shipped
Savings Date missing for many 2026 deemed claims
In our testing we compared the deemed claims CEDARS “Savings Date” column in the record-level Claims 2026 download to SDGE & SCG internal systems. This revealed a large number of blank “Savings Date” values for deemed claims in the CEDARS record-level download. We believe all deemed claims should have “Savings Date” populated there.
Add missing fields to the Active dash output download to match Confirmed dash download
As a Program Administrator, I want Active and Confirmed Dashboard downloads to have the same fields. While investigating the SavingsDate field, we identified broader inconsistencies between the Active and Confirmed Dashboard downloads. Review the purpose of each download and define a consistent approach to: included fields, naming conventions, intentional differences, and opportunities to align or consolidate the downloads.
Participant table - add ability to remove ParticipantCount records
Program Administrators need the ability to remove previously submitted ParticipantCount records in cases where overriding the data is not sufficient. Currently, validation rules do not allow ParticipantCount values of 0, preventing the removal of records through a new upload. Update the ParticipantCount submission process so that each new Participant table submission replaces any previously submitted ParticipantCount records. Only the records included in the latest submission would be retained.
Regression testing SavingsDate
Feedback from Greg “The attached file downloaded from CEDARS shows the SavingsDate field at the end of the Claims table. The SavingsDate field is no longer part of the 2026 input spec but will be added to the record-level output file.” Investigate if the SavingsDate output is behaving as expected for 2026
Claim Spec - Update EquityTargeted data rule description on the Participant table
Update the EquityTargeted data rule description on the Participant table to: Number of participants qualifying as Equity Targeted. A program participant that meets the CPUC-adopted criteria for being Hard-to-Reach, or being located in a disadvantaged community, or considered underserved.
Re-order Claim Spec fields to match CET ordering
The quarterly csv files for SDGE and SCG were reordered to match the published Claims_2026_Inputs.csv document. SDGE and SCG 2026 quarterly csv files successfully uploaded to CEDARS-2. The CET returns an error when using the Measure.csv and ProgramCost.csv files from the quarterly upload. “Measure.csv: The columns are in the wrong order ProgramCost.csv: The columns are in the wrong order” This worked before the 2026 spec changes.
Provide Record-Level Field Mapping for New Inputs and Outputs
To support upstream system updates and integration activities, stakeholders have requested additional documentation showing where newly introduced input and output fields will appear within record-level downloads. In particular, Greg requested visibility into: - Which new fields have been added - The position of those fields within each record-level file - Example values for each new field - There is a strong preference for newly introduced fields to be appended to the end of record-level
Unable to upload claims without ProgramCost table - Update Participant.PrgYear data rule
When I try to upload a claims file with only the Measure, Claim, Site, ContactClaim, and Participant tables (i.e., without ProgramCost) as an XLSX file, I encounter a server error. I tested this with both the example claims file and some of my PA’s claims. I didn’t see any issues uploading an XLSX file with all tables or only with the ProgramCost table. New Update (7/28): The specific validation rule that triggered the error is: Participant.PrgYear must match a valid ProgramCost.PrgYear. Update this validation rule to be: Participant.PrgYear is for the current claim year. This matches one of the validation rule applied to Measure.ClaimYearQuarter
Census Tract Field Requirement Discrepancy
I noticed a discrepancy with the Census Tract field requirements. The field requirement is 11 characters per the ticket (https://cpuccedars.featurebase.app/p/geospatial-visualisation-of-claims-data). While the CEDARS specification page itself appears to correctly show the field length as 11 characters https://cedars-2.cpuc.ca.gov/claims/specification/pii/site/, the Download All Data Rules from the specification page lists it as 10 characters (see attached images). Could the team please review and update the documentation as required?
Participant Count Validation Error
During Claim Spec UAT, record-level validation errors were encountered when loading Participant records with large participant counts. The system rejects records when Participant.ParticipantCount exceeds 32,767, displaying the following validation message: "Ensure this value is less than or equal to 32767." This limitation does not appear sufficient for programs with large participant populations and may prevent submission of valid participant data. Test case: https://cedars-2.cpuc.ca.gov/claims/upload-summary/833/ Sample records: PGE_Res_002a|2026|Households: Participant.ParticipantCount = 57,972 PGE_Res_002d|2026|Households: Participant.ParticipantCount = 3,300,000