Standard Energy Efficiency Data (SEED) Platform™ is a web-based application that helps organizations easily manage data on the energy performance of large groups of buildings.
When requesting filtered properties with the /api/v3/properties/filter/ endpoint, if you leave out the cycle param the backend defaults to the first alphabetical cycle
What's this PR do?
Makes the cycle id explicit, so that when you're on the Inventory List page, select records, and open the merge modal, it will now work for all cycles and not just the first alphabetical cycle
Fixes the cycle toggle on the map page, it was also affected by this issue
Adds a fallback on the front-end, such that if a cycle isn't passed when filtering properties it will use the most-recently selected cycle
How should this be manually tested?
In an org with multiple cycles, go to the Inventory List page and select any cycle that is not alphabetically sorted first
Select a few records, and then open the Merge modal
Ensure that the data appears as expected
Go to the Inventory Map page
Toggle between different cycles, ensure that different (and correct) data appears for each cycle
perryr16
commented
2 months ago
Any background context you want to provide?
When requesting filtered properties with the
/api/v3/properties/filter/endpoint, if you leave out thecycleparam the backend defaults to the first alphabetical cycleWhat's this PR do?
How should this be manually tested?
In an org with multiple cycles, go to the Inventory List page and select any cycle that is not alphabetically sorted first
Select a few records, and then open the Merge modal
Ensure that the data appears as expected
Go to the Inventory Map page
Toggle between different cycles, ensure that different (and correct) data appears for each cycle