update<Type> mutation
Use the updateTYPE GraphQL mutation to modify Dropbox entities.
Mutation syntax
The following code illustrates required format for the GraphQL request, followed by a description of the input values:
mutation {
updateTYPE(identity: {
namespace: "NAMESPACE",
id: "IDENTIFIER",
type: "TYPE"
},
input: {
INPUT_FIELD_1: INPUT_VALUE_1
INPUT_FIELD_2: INPUT_VALUE_2
INPUT_FIELD_n: INPUT_VALUE_n
} )
{
RESPONSE_FIELD_1
RESPONSE_FIELD_2
RESPONSE_FIELD_n
}
}
Fields and inputs
- updateTYPE
- The operation to be performed by the mutation (update) and the type of entity to be acted upon. The TYPE is the CRM entity type and matches the TYPE value in the identity section.
- identity
- The
identityobject is formed from the following field values to uniquely identify the entity to be updated:- namespace
- Where NAMESPACE is that of the external entity.
- id
- Where IDENTIFIER is the unique identifier provided by the external system.
- type
- Where TYPE refers to the external entity type.
- localId
- Where LOCAL_ID can be either a Publication ID or a locale string, such as 'en' or 'sv-se', which identifies a locale-specific variant of the entity.
- input
- The
inputobject includes property-value pairs that define the entity to be updated, where:- INPUT_FIELD_1 to n
- The property to be defined for the new entity.
- INPUT_VALUE_1 to n
- The input data for the entity.
- Response fields
- (Optional) Fields at the end of the request identify data that you want to return in the response following a successful update operation.
Example request and response
The first sample code block illustrates a request to update details for a Contact entity. The second code block illustrates the corresponding response with a confirmation of the entity's identity and the updated Contact details.
| Request | Response |
|---|---|
| |