You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since API v46, the response for the Upsert Request has changed in two significant ways
The created parameter has been added to the successful response object.
Updates now return a 200 OK with a full body response instead of an empty response.
Previously I'd been using the existence of an Id in the response to indicate that the Upsert had created an object, and the lack of one to indicate an update to an existing object - this is no longer true.
At the moment, my code doesn't do much apart from logging the difference, but this might be more of an impact for others.
Does anyone else see the need to expose the Created property?
Should this just be added to the standard SuccessResponse object, or should we look to modify the calls used by upsert from the general Patch requests to UpsertPatch requests that return an UpsertSuccessResponse?
The text was updated successfully, but these errors were encountered:
Since API v46, the response for the Upsert Request has changed in two significant ways
created
parameter has been added to the successful response object.Previously I'd been using the existence of an
Id
in the response to indicate that the Upsert had created an object, and the lack of one to indicate an update to an existing object - this is no longer true.At the moment, my code doesn't do much apart from logging the difference, but this might be more of an impact for others.
Created
property?SuccessResponse
object, or should we look to modify the calls used by upsert from the general Patch requests to UpsertPatch requests that return anUpsertSuccessResponse
?The text was updated successfully, but these errors were encountered: