When writing records via APIv4, the use of joins can implicitly reveal information about inaccessible records.
The updated version of CiviCRM imposes new limits on the use of joins within write operations.
The limitations are expected to have minimal impact on ordinary/legitimate callers. However, some API callers may
experience a new error (e.g. No unique index on ENTITY.FIELD.). If you are affected, then you may wish to:
- Replace the use of inline join. Instead, split your API call into multiple calls. (One call to lookup data; and another to write data.)
- File an issue in https://lab.civicrm.org/dev/core/ describing the intended usage and the new error.
CiviCRM v6.19.2 and earlier
CiviCRM v6.19.3, v6.16.6 (ESR), and later
Upgrade to a fixed version of CiviCRM
(Alphabetically) Coleman Watts (CiviCRM), Jakub Fidler, Luke Stewart (Fuzion), Seamus Lee (JMA Consulting), Tim Otten (CiviCRM)
