I am astounded by how badly the JSON Entry Dialog is broken - is nobody using or testing this?
I am trying to build a Webhook block in a Guided Conversation. First, it's nuts how little integration there is from Desk to itself - why do I need to build a webhook to create a new ticket from a conversation? Is that not very likely to be THE primary use of this feature?
Anyway, as I'm trying to use the incomplete API documentation to get this to work, I'm entering the JSON body of my request, and I've run into the following:
- If you type the "@" symbol into the JSON editor dialog, it always brings up the "Search Variables" dialog - there is literally no way to type that symbol into the box. I had to copy/paste it from elsewhere to get it to work
- I have entered perfectly valid JSON as validated by multiple online JSON validation services (and the fact it's very simple with only a few fields) and yet am getting a "Duplicate key found" error that won't even let me save what I've got. Can you spot the duplicate key?
So frustrating when it seems like every time we try to go down a path that seems like it should be obvious we end up fighting against nonsensical stuff.
Turns out the "Duplicate key" is because it wants to treat `departmentId` as a string even though it's listed as a `long` in the documentation.