Market Facing Bugfixes:
Cannot submit app when interconnecting Utility Changed Between Part 1 and 2 (from ComEd).
Issue: When a Part I project application was originally submitted with the Interconnecting Utility specified as ComEd, but the Interconnecting Utility was later updated/corrected to a different utility company during Part I Verification, submission of the Part II application was being blocked by a validation error requesting to have a Net Metering Letter uploaded in the documents section. This document requirement is unique/specific to projects where the Interconnecting Utility is ComEd and should not apply to these projects.
Fix: Part II submission logic has been updated to account for this scenario.
Spanish Disclosure Form does not auto populate Today’s Date in the Signature section.
Spanish DG Disclosure Forms being signed from the eSign process, were not populating the date signed field on the PDF. The eSign audit trail included on the PDF and completion date of the Disclosure Form were properly reflecting the date signed. Disclosure Forms in English and all Community Solar Disclosure Forms were not affected. The bug has been corrected and the Date Field on PDFs is now being populated on Spanish DG Disclosure Forms upon eSignature.
Spanish DG Disclosure Forms: Lease and PPA Information and Costs section shows incorrect data in PDF.
When an AV generates a Spanish version of the Lease or PPA Disclosure Form, the “Information and Costs” section will now show the correct data for the following questions for each of the forms:
Lease – Length of lease will now show both the month and year on the PDF.
First Payment → When payment is due will now show data for when the first payment is due.
PPA – Length of contract will now show both the month and year on the PDF.
First Payment → When payment is due will now show data for when the first payment is due.
Market Facing Enhancement:
API – Enhanced Validation Error Messaging.
Several validation messages have been returned by the API when an error is observed in three specific fields. This has been updated to more clearly call out the name of the missing attribute and remove double quotes from the error message text, which can cause parsing issues when relaying the message back resulting in a generic “bad request” error message in place of the detailed error.
The affected fields/key-value pairs are [netmetering_excess_generation_credit], [energy_storage_rebate_recipient], and [netmetering_excess_generation_credit]. This change does not require any action from participants using the API.
Expose Schedule A and B reports for AVs.
An AV will now be able to view and export Schedule A and Schedule B reports in the Portal, under the Contracts Menu. They will be able to see all Schedule A and Schedule B data associated with their Vendor ID and in addition will be able to export a CSV of this data in full or filtered to the filter criteria they pick on the dashboard.
NM2-Cleanup – API Call – remove alt validation logic to support old calls.
The Disclosure Form API has been updated to deprecate/remove Rebate_Amount key-value pair on DG Disclosure Forms when creating from the API. When net metering originally went live on January 7, 2025, it included new functionality to calculate the amount of Smart Meter rebates based on a new rebate rate field, but initially the method of supplying an explicit Rebate Amount to override the calculation was supported for backward compatibility during rollout. As Rebate Rate is not a required field in DG Disclosure Forms utilizing a rebate, the Rebate Amount key-value pair was no longer needed.
Part I Application Enhancement: Conditional message on Documents page for expansion and co-location projects (COC|PTO).
A message has been added to the top of the Documents section of Part I Applications for expansion and co-location projects to inform AVs what optional documents are required to apply for exceptions to expansion pricing.
DF Enhancement: Updated Collateral Amount and Fee Guidance (DG Purchase).
The Collateral Fee question on Disclosure Forms for DG-Purchase projects has been updated with additional guidance clarifying when a Collateral Fee should be listed in Fees Table verses when it should be listed in the explicit Collateral Fee field.
