Recherches récentes
Pas de recherche récente

Mark Ross
Adhésion le 06 déc. 2024
·
Dernière activité le 04 mars 2025
Suivis
0
Abonnés
0
Activité totale
3
Votes
0
Abonnement
1
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Mark Ross
Mark Ross a ajouté un commentaire,
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.
Afficher le commentaire · Publication le 04 mars 2025 · Mark Ross
0
Abonnés
0
Votes
0
Commentaire
Mark Ross a créé une publication,
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.
Publication le 06 déc. 2024 · Mark Ross
0
Abonnés
3
Votes
3
Commentaires