Recent searches
No recent searches

Martin Seo
Joined Apr 16, 2021
·
Last activity Oct 27, 2021
Following
0
Followers
0
Total activity
2
Votes
0
Subscription
1
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Martin Seo
Martin Seo commented,
Hey Mark and Randy,
I was able to figure this out after Googling and Frankensteining a couple Community posts together.
The json used in my trigger was:
{"ticket":
{"custom_fields":
[{"id":custom_ticket_field_id,
"value":"{{ticket.requester.organization.custom_fields.field_key}}"}]
}
}
The bolded portions are what you should be filling out with a custom value.
For the ticket, the id is the custom field ID
For the organization, however, the field key is NOT the field id. You have to go to Manage > Organization Fields and use the Field key that pops up on the right when you click on an organization field.
Let me know if this works out for you guys.
View comment · Posted Feb 05, 2019 · Martin Seo
0
Followers
0
Votes
0
Comments