Fix #613 - Fixed Error Occurring If First Report Field Is a Custom Field #614
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.
Description
Lines 1245 to 1247 of AOR_Report.php were in the wrong order causing the first iteration of the loop to return an empty $data array which in turn caused the generated query to fail if a custom field was used as the first field:
I simply inverted the lines and can confirm that reports work properly after applying the fix
Motivation and Context
This fix is necessary to correctly manage custom fields when used as first field of a report
How To Test This
Create a report using a custom field as the first field of the report
Types of changes
Final checklist