APIv3 - Don't handle custom data already handled by BAO
authorColeman Watts <coleman@civicrm.org>
Thu, 21 Jul 2022 14:36:06 +0000 (10:36 -0400)
committerColeman Watts <coleman@civicrm.org>
Thu, 21 Jul 2022 20:11:31 +0000 (16:11 -0400)
commitf54abaaec0bf6109b5b39a46979145e6bc685645
tree8671f0ebc7824a40f664b2eab282376543da63c7
parent2265be8bde8b675c6940f4c59927c6612717acb2
APIv3 - Don't handle custom data already handled by BAO

Fixes dev/core#3747
It's confusing to handle saving custom data in the APIv3 layer,
because APIv4 expects the BAO to handle it.

Until every BAO consistently uses WriteRecord this will continue to be a pain point.
CRM/ACL/BAO/ACLEntityRole.php
CRM/Core/BAO/ActionSchedule.php
CRM/Core/BAO/Domain.php
CRM/Core/BAO/RecurringEntity.php
CRM/Core/BAO/Website.php
CRM/Mailing/BAO/Mailing.php
CRM/Member/BAO/MembershipBlock.php
CRM/Pledge/BAO/PledgeBlock.php
api/v3/utils.php