최근 검색
최근 검색 없음

Mark Ross
가입한 날짜: 2024년 12월 06일
·
마지막 활동: 2025년 3월 04일
팔로잉
0
팔로워
0
총 활동 수
3
투표 수
0
가입 플랜
1
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Mark Ross
Mark Ross님이 에 댓글을 입력함
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.
댓글 보기 · 2025년 3월 04일에 게시됨 · Mark Ross
0
팔로워
0
투표 수
0
댓글
Mark Ross님이 에 게시물을 만듦
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.
2024년 12월 06일에 게시됨 · Mark Ross
0
팔로워
3
투표 수
3
댓글