From 809a95729498ee9f760ae4ecadd26960139d3321 Mon Sep 17 00:00:00 2001 From: joshmsamuels Date: Thu, 12 Sep 2019 12:22:28 -0400 Subject: [PATCH] Updated docs to document the api change which prevents managed fields during a server-side apply (#16320) --- content/en/docs/reference/using-api/api-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/reference/using-api/api-concepts.md b/content/en/docs/reference/using-api/api-concepts.md index c989fd1a1f..ed6b14f484 100644 --- a/content/en/docs/reference/using-api/api-concepts.md +++ b/content/en/docs/reference/using-api/api-concepts.md @@ -475,7 +475,7 @@ a little differently. For instance, only the apply operation fails on conflicts while update does not. Also, apply operations are required to identify themselves by providing a `fieldManager` query parameter, while the query parameter is optional for update -operations. +operations. Finally, when using the apply operation you cannot have `managedFields` in the object that is being applied. An example object with multiple managers could look like this: