UpdateCustomerInput

UpdateCustomerInput

Input for updating a RollerUp customer.

Field semantics:

• Omitted fields are unchanged.
• For email and phone, an explicit null clears the field. name cannot be cleared.

Constraints:

• A customer must always have at least one of email or phone. An update
  that would leave both null is rejected with a VALIDATION error.
• Updating email to a value already used by another customer in the same
  company is rejected with a CONFLICT error (code: CUSTOMER_EMAIL_CONFLICT,
  with conflictingCustomerId in extensions) so the client can prompt a merge.

Kind: Input

Fields

Definition

"""
Input for updating a RollerUp customer.

Field semantics:
- Omitted fields are unchanged.
- For `email` and `phone`, an explicit null clears the field. `name` cannot be cleared.

Constraints:
- A customer must always have at least one of `email` or `phone`. An update
  that would leave both null is rejected with a VALIDATION error.
- Updating `email` to a value already used by another customer in the same
  company is rejected with a CONFLICT error (code: CUSTOMER_EMAIL_CONFLICT,
  with `conflictingCustomerId` in extensions) so the client can prompt a merge.
"""
input UpdateCustomerInput {
  """Customer email. Omit to leave unchanged; pass null to clear."""
  email: EmailAddress
  """Customer ID"""
  id: ID!
  """Customer name. Null/omitted is treated as no change."""
  name: String
  """Customer phone. Omit to leave unchanged; pass null to clear."""
  phone: PhoneNumber
}