PATCH contacts/v1/contacts - Attribute reverts back to assigned default value when not included in payload
Last updated 2022-03-30 ·Reference W-9946166 ·Reported By 2 users
When making a PATCH call to the contacts/v1/contacts route targeting an attribute group with an attribute that has a "default value" assigned and that attribute is NOT included in the API payload, that attribute value will be set back to the default value even if the contact has another value specified.
1) Create an attribute group with an attribute that has a default value.
2) Make a PATCH call to contacts/v1/contacts that does not include the attribute above.
Always include the fields with default attributes in the PATCH call with the desired value.
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.