Have something to say?
Buggy UI when saving filters in Custom Permutation Report
Issue: The Custom Permutation Report filtering widget has buggy UI issues when configuring and saving filters. An unsupported icon/image is displayed at the top of the filtering panel and the individual filter widget. Additionally, when applying a filter, the filtering widget just freezes and does not do anything. However, if you ignore the unresponsive “apply” button and save the report, you do see that the filters were applied successfully and correctly. Business impacts: The bug creates confusion and uncertainty when configuring Custom Permutation Reports, increasing the risk of incorrect report configurations and requiring additional time to verify results. The unsupported icon took up most of the page.
eTRM Public Database Isn't Syncing - Published Tables
Issue: The eTRM system alarm detected discrepancies between the public database and the main eTRM database, identifying a sync failure with the public sync since the last manual sync on 7/28. This only affects the published tables of the database; the data tables sent to CEDARS for the load shape process were not affected. Business impact: Outdated or incomplete measure data was sent to downstream users and applications, which may have affected business analysis. Four published measures and their permutations were missing. Their previously published PY2026 versions were missing EndDate, added after the approval of the published versions.
Deleting Custom Permutation Report redirect you to Dashboard
Issue: When deleting a custom permutation report, the application redirects you all the way back to the Home Dashboard page, instead of just the “Permutations” tab of the measure you were looking at. Steps to reproduce: Navigate to a measure Click on the Permutations tab Create and save a custom permutation report if there is none Click on the custom permutation report again and delete the report eTRM brings you all the way back to Home page Business impact: Users are likely to continue managing the custom permutation report of the measure they were viewing. By redirecting the user all the way back to the dashboard, it’s quite inconvenient and time-consuming to go back to the measure.
Invalid Calculation
Issue: Calculations using the “BasisValue” column of the shared Effective Useful Life and Remaining Useful Life value table result in validity error. However, the equation is still evaluated correctly in the permutation. Business Impact: Unknown or potentially false validity error, creating confusion and low confidence with the calculation. Reporter: Nicholas Fette (Solaris Technical)
eTRM Public Postgres Database Isn't Syncing
Issue: The eTRM public Postgres database has not synced since 7/21/2026 ~9 am UTC (~2 AM PST). This is the day we ran the 2026 CET correction update. The database data showed the last updated date was 7/21/2026. Measure activities (e.g., new drafts and new permutations) beyond that date are not reflected in the database after the scheduled sync time. Business Impact: The public PostgreSQL database contains outdated data, preventing users and downstream systems (especially the CEDARS Load Shape Library) from accessing the latest production updates. This resulted in inaccurate reporting and data discrepancies between the public database and the production eTRM system.
Strip Leading and Trailing Blank Space in eTRM Fields
Background eTRM currently accepts and stores leading and trailing whitespace entered into text fields (e.g., “Technology ID” value table). While editing a value, the whitespace is visible. However, after saving, the UI trims the whitespace for display in both the Value Table and the Permutation Table, making it appear as though the value has been cleaned. The whitespace is still present in the underlying data and is returned in downloads, the API, and the database. This inconsistent behavior makes the issue difficult to detect during quality control. In our case, the hidden whitespace caused a downstream validation error in the CEDARS Load Shape Tool (the Tool did not generate the avoided cost for the measure), but the root cause was not immediately apparent because the UI displayed the value without the whitespace. Solution: eTRM does the automatic stripping across the board (not just in the display) Steps to reproduce: Navigate to a measure Create or click on an existing value table Edit the value table column that is of text data type Save the edit Map the field to the per
Remove the "Delete [Measure]" option from the measure properties page
Remove the "Delete [Measure]" option from the measure properties page (not MPD). This is currently causing an error because you need to take a draft to delete
Replace "Published Date" with "Effective" and "End" dates on web pages
Published date is among the less important dates to show on high-level webpages. For instance, when wanting to learn which lighting measure packages are currently in the catalog (Measures tab), I had to go to SWLG012-01 to see that it expired 2020-12-31 and that no more recent version exists. It would be ever so much more helpful to list the Effective and End dates on this page rather than the published date. Agree that publish date is not very valuable, but versions are grouped together in the log, so it would be hard to display start/end dates. Maybe just remove publish date.
500 Server Error when Start Date is Removed
When the “PA Lead” field is removed, eTRM prompts an error message that the field is required. When the “Start Date” field is removed, eTRM produces a 500 Server Error. Low priority since Start Date should never be removed.
Eliminate timeout issues when exporting large permutation tables
COMBINE w/ E#200. Eliminate timeout issues when exporting permutation tables