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

SearchKit - Fix display of contact reference fields (single-value) #20117

Merged
merged 1 commit into from
Apr 21, 2021

Conversation

colemanw
Copy link
Member

Overview

This fixes the display of contact reference fields, giving feature parity with other FK fields. Both ID and Display Name are shown as available columns.

Ref https://lab.civicrm.org/dev/core/-/issues/2553

Before

ContactRef Display Name column shows error in header and no data.

After

Display name works correctly.

Comments

This does not address the more difficult question of how to join multi-valued contact reference fields with contact display names.

@civibot
Copy link

civibot bot commented Apr 21, 2021

(Standard links)

@civibot civibot bot added the master label Apr 21, 2021
@kurund
Copy link
Contributor

kurund commented Apr 21, 2021

@colemanw

Thanks. This PR fixes the issue with the contact reference field display.

One related query, is there a way to make it clickable? I don't get this contact option in the links drop down.

This fixes the display of contact reference fields, giving feature parity
with other FK fields. Both ID and Display Name are shown as available columns.

This does not address the more difficult question of how to join
multi-valued contact reference fields with contact display names.
@colemanw colemanw force-pushed the searchKitFixContactRef branch from 1cbd793 to ede387b Compare April 21, 2021 22:10
@colemanw
Copy link
Member Author

Ok. I added a unit test so we can merge now based on review & tests passing.

@colemanw colemanw merged commit c926d5a into civicrm:master Apr 21, 2021
@colemanw colemanw deleted the searchKitFixContactRef branch April 21, 2021 23:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants