Ricerche recenti
Nessuna ricerca recente

Mark Ross
Data ingresso 06 dic 2024
·
Ultima attività 04 mar 2025
Seguiti
0
Follower
0
Attività totali
3
Voti
0
Abbonamento
1
PANORAMICA ATTIVITÀ
BADGE
ARTICOLI
POST
COMMENTI NELLA COMMUNITY
COMMENTI AGLI ARTICOLI
PANORAMICA ATTIVITÀ
Ultima attività di Mark Ross
Mark Ross ha commentato,
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.
Visualizza commento · Data ultimo post: 04 mar 2025 · Mark Ross
0
Follower
0
Voti
0
Commenti
Mark Ross ha creato un post,
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.
Data ultimo post: 06 dic 2024 · Mark Ross
0
Follower
3
Voti
3
Commenti