Pesquisas recentes
Sem pesquisas recentes

Mark Ross
Entrou em 06 de dez. de 2024
·
Última atividade em 04 de mar. de 2025
Seguindo
0
Seguidores
0
Atividade total
3
Votos
0
Assinatura
1
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Mark Ross
Mark Ross comentou,
James Peterson - Eastern Logic no I haven't been able to resolve it. I'm not updating a drop-down field. Just a custom field with a free text value. The custom field needs to be updated as soon as the ticket is opened, but I can't update it due to this validation error message. The field is only conditional on the ticket being submitted, but I'm not trying to submit the ticket, merely update a custom field.
Exibir comentário · Publicado 04 de mar. de 2025 · Mark Ross
0
Seguidores
0
Votos
0
Comentários
Mark Ross criou uma publicação,
I'm trying to update a custom field value via the API. I'm using a PUT request to /api/v2/tickets/.json I'm getting a validation error as follows:
{
"error": "RecordInvalid",
"description": "Record validation errors",
"details": {
"base": [
{
"description": "Incident vs. Service Request: needed",
"error": null,
"ticket_field_id": 21621964218653,
"ticket_field_type": "FieldTagger"
}
]
}
}
The “Incident vs. Service Request” field is not the field I'm updating. I assume there some is configuration that is making this field required when updating a ticket, although I can't figure out what that config might be? The field has “Required to solve a ticket” enabled, but I'm not trying to solve a ticket, and there are other fields with this setting which don't cause the same problem. Can anyone help me out?
Thanks.
Publicado 06 de dez. de 2024 · Mark Ross
0
Seguidores
3
Votos
3
Comentários