search

US-EPA-CAMD / easey-ui

Project Management repo for EPA Clean Air Markets Division (CAMD) Business Suite of applications
MIT License
0 stars 0 forks source link

Bug: Viewing Emissions Data #5803

Open acollad1 opened 8 months ago

acollad1 commented 8 months ago

Issue: UI should only allow users to select a reporting period that actually exists in the emissions evaluation table for that monitoring

Error when trying to view emissions data in global: "insert or update on table "emission_view_count_2022_q1" violates foreign key constraint "fk_emission_view_count_emission_evaluation" Steps to Recreate:

  1. Navigate to Lamar in emissions module
  2. Select 2022 Q1 and combined paramter view
  3. The error shows at the top

Private Zenhub Image

jwhitehead77 commented 8 months ago

@AbuFofanah the reason for this error is becasue the facility did not operate in 2022 Q1 and did not report any data. There is not any data for this mp/qtr in any of the emissions tables. We need to look at only having reporting periods in the dropdown that actually have data and the refresh procedures should not try to refresh data if nothing reported

annalbrecht commented 3 months ago

Verify if this is still an issue.

lgiannini1 commented 2 months ago

On dev and tst, I was able to select a reporting period which had no data (2022 Q1)for ORIS 508, unit 8. I was able to replicate the error message on tst, but the error message on dev has been updated.

dev: Image

tst: Image

annalbrecht commented 2 months ago

Question for Chris: Should the quarters show up to select if data was not submitted for them? Or should it be available to select and then a message is returned? Is there a consistent way of doing this already?

Discussed with Chris on 4/9/24: Leave functionality as is in Dev. But we need to figure out why this is not on Test.

ibarra-michelle commented 1 month ago

@annalbrecht we discussed this ticket internally and would like to deprioritize this to Phase 1B. Could you please relabel this? Thank you.

FYA - This ticket was deprioritized since it isn't a blocker for industry submission and is a low priority compared with other development work.

ibarra-michelle commented 3 weeks ago

@annalbrecht - could we relabel this from P-1B to 2025 (Q1 or Q2)? Internally, we discussed this ticket and are prioritizing other functionality. If the dev team has any questions, we can discuss them at the next meeting.

Also, should we link this ticket #5803 to #6046 CO2 Calculation View? They seem related.

annalbrecht commented 3 weeks ago

@ibarra-michelle I don't think #5803 and #6046 are related.