Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CRM-21447: Relationship Report: move variable handling to beginPostProcessCommon #11293

Merged
merged 1 commit into from
Nov 17, 2017

Conversation

mlutfy
Copy link
Member

@mlutfy mlutfy commented Nov 17, 2017

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() to beginCommonPostProcess().

Comments

You can test from the API Explorer:

  • Create a report instance of contact/relationship that has a filter on "relationship Type" = ""
  • Take note of the instance_id
  • Go to the API Explorer (civicrm/api/explorer), and run: ReportTemplate.getrows with variable: instance_id=1234 (where 1234 is your instance_id noted above).

@eileenmcnaughton
Copy link
Contributor

This is totally consistent with the purpose of introducing the beginPostProcessCommon function. I feel confident enough about this to merge based on a read of the code

@eileenmcnaughton eileenmcnaughton merged commit 788e77e into civicrm:master Nov 17, 2017
@eileenmcnaughton eileenmcnaughton deleted the crm21447 branch November 17, 2017 22:55
sluc23 pushed a commit to ixiam/civicrm-core that referenced this pull request Jan 10, 2018
CRM-21447: Relationship Report: move variable handling to beginPostProcessCommon
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants