[TEMPORARY FIX] Data Export doesn't work when using withAvg() #1560
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
⚡ PowerGrid - Pull Request
Welcome and thank you for your interest in contributing to our project!. You must use this template to submit a Pull Request or it will not be accepted.
Motivation
Description
This Pull Request is a temporary fix for problems exporting data under certain conditions, for example when using
withAvg(). While I had this problem in the Demo, I could not replicate the bug in the tests.In the bug I encountered, the Exception is thrown because
WithExporttries to access a field that doesn't exist. This doesn't prevent data being exported, as existing fields will be included in the CSV/XLS. However, the Exception will impact the user experience.I decided to add a
rescure()to let the application continue running, but this is NOT A FIX and we should continue investigating the issue.Related Issue(s): #1540
Documentation
This PR requires Documentation update?