Forum Discussion
6 years ago
Correction on the above - I do see that "id" can also work but results in the same thing. I was just going off of what I was aware of as "proper" path syntax... but in any case, it still seems to work that way. So, again, the main issue now seems to be the extra text added to the ##EXTERNALTICKETID## property which has nothing to do with the JSON response AFAIK.