CRM-21447: Relationship Report: move variable handling to beginPostProcessCommon #11293
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
For 99.99% of users, this should not have an impact. However, for people accessing the report from the APIv3, this fixes using a report instance where the report filters on a
relationship_type_id
. It also fixes a bug when exporting report data with the Export to Excel extension.Before
fatal error
Unknown column '11_b_a' in 'where clause'
After
no fatal error 🌈
Technical Details
I moved a hack from the
postProcess()
tobeginCommonPostProcess()
.Comments
You can test from the API Explorer:
contact/relationship
that has a filter on "relationship Type" = ""instance_id
civicrm/api/explorer
), and run:ReportTemplate.getrows
with variable:instance_id=1234
(where 1234 is yourinstance_id
noted above).