I think we are going to need to track the acoustic reference against groups that have been created - my data flows are moving around but they all suggest that tracking the remove ID is going to be helpful...
Description
Details
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Eileenmcnaughton | T301514 Civi Searchkit should allow user to export list to acoustic | |||
| Resolved | Eileenmcnaughton | T304473 Add api to add contact to a group in acoustic | |||
| Resolved | Eileenmcnaughton | T304475 Create custom field data structure to store the acoustic reference |
Event Timeline
Change 772973 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Add a custom field group to store the Acoustic group ID
Change 774582 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Store remote group ID to the custom field
Change 774587 had a related patch set uploaded (by Eileen; author: Eileen):
[wikimedia/fundraising/crm@master] Add groups to Acoustic data fetch output
Change 772973 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Add a custom field group to store the Acoustic group ID
Change 774582 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Store remote group ID to the custom field
Change 774587 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Add groups to Acoustic data fetch output