Michael Bennett

Greg, that explanation doesn't follow. As Miroslaw pointed out, you can use the ticket fields, targets, and webhooks you're creating in many places in the requirements file: in the actions of triggers, automations, and macros, and in the conditions of triggers, automations, and even views. You use the key of the dependency being created. I've successfully used this extensively. But in views, adding the key of the new ticket field to the output property, and both Miroslaw and I would like to know why.

It cripples creating views in the requirements.json. If you want to display any of the custom data your app is creating in the view, you'll have to create the view after installing the app. Worse yet, if you ever have to uninstall and reinstall the app, you'll have to re-add those fields.

I hope this is something Zendesk is aware of and working on, hopefully along with allowing the creation of custom forms in the requirements file.

I was able to resolve my problem. I had created a wrapper around the ZAF client, but failed to bind some of the methods to the client, so at some very late point in the app lifecycle the modal broke.

I was able to resolve my problem. I had created a wrapper around the ZAF client, but failed to bind some of the methods to the client, so at some very late point in the app lifecycle the modal broke.

Tipene Hughes and Benessa Dumol, I'm having the same issue. Can you share how this was resolved?

I do note one difference: the error I get says it cannot access the GUID of the current client, not the modal client.

Rebecca Dai and Eric Nelson, I know this is from years ago, but I'm having the same exact problem: I can't re-create a modal and get the yellow script error. It looks like y'all successfully solved the problem in a ticket, but I'd be keenly interested to know how you did it.