REST API Data Events - Increment Column Value - not matching on composite primary key
Trailblazer Community

REST API Data Events - Increment Column Value - not matching on composite primary key

Marketing Cloud API

Last updated 22 days ago ·Reference W-3805669 ·Reported By 2 users

Fixed in version Marketing Cloud Release May 2020

Summary
The REST API 'increment a column value by data extension external key' PUT call does not properly match records in data extensions defined with composite keys, and will update all records that match the first part of the key.

Repro
Method: PUT
Endpoint: https://www.exacttargetapis.com

Data Extension with two primary keys: 'key_a' and 'key_b' and one other field called 'Value' . All are data type numeric.

When specifying only 'key_a' OR 'key_b' in the PUT call, records with the specified key value get updated
When specifying 'key_a' AND 'key_b' in the PUT call, all records with the 'key_a' value get updated, instead of the records with both the 'key_a' and 'key_b' value. This is regardless of the order of the key names in the PUT call.

Workaround
At this time, do not use composite keys via REST API.

Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.