Skip to main content

Claims table validation is looking for a sort order

Testing Feedback

PAs receive errors if their records are not sorted in the same order across Claim & ContactClaim tables. This should not be the case. CEDARS shouldn’t care about an order.

Environment
Staging cedars-2
Select user type
Posted by cedars team ·
Status: Completed2 comments

Log in to comment and vote

Comments2

  • cedars team

    Team•

    Aug 21, 2024

    Feedback from SCE:
    Additional feedback suggests that the logic of this rule will need to change so that the Claim.ClaimID is the same as one or more ContactClaim.ClaimID. This could resolve the sort issue 🤞.

    https://cedars-staging.sound-data.com/claims/upload-summary/284/

    File for testing
    284_2024_05_Q2_1707_Deemed_Sorted.xlsx

    Rule that needs to be tweaked

    Claim.ClaimID is the same as ContactClaim.ClaimID when Claim.ClaimID does not end with one of ('Audit', 'Placeholder') and Measure.MeasImpactType does not start with 'Cust-NMEC-Pop' and Program.ProgramCategory does not equal 'Energy Savings Assistance' and Program.ProgramSegment does not equal 'Codes and Standards'.

  • cedars team

    Team•

    Aug 16, 2024

    Feedback from PGE: As discussed, the CEDARS ClaimID rule appears to be looking for the order to match between Claim and ContactClaim. As long as the Claim.ClaimID existed in ContactClaim, it was sufficient in the past. The order did not matter. SiteID order does not appear to be an issue.