Prevent hard-fail when section header / group by option chosen on logging report #11953
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
|
test this please |
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.
Overview
Prevent hard-fail when section header / group by option chosen on logging report
The contact logging summary report permits 'Section Header / Group By' in the order by tab but it doesn't work, badly.
Before
After
Or by contact
Technical Details
I'm not convinced the option is terribly valid /important in this report but if chosen it should not give a fatal error. I tested 2 criteria & both gave a fatal. This is just a quick fix to prevent that. It does not populate the count - hence the empty brackets but I see that as low priority - perhaps no-one will ever care level of issue