Unable to add any sort of private metadata to tickets in new SDKs?

Greg Katechis is there any further updates on this? I'm currently working on integrating the Support SDK and discovered I can create custom fields but like the OP, I could only set a value for these fields by making the field customer editable in the admin portal.

You mentioned above that these fields can still be hidden from the end users - how do you do this?

Hi Seth! I learned that this feature will be coming to our SDKs in the coming month! I was informed that the only difference from what you had noted above in your three points was that the field would be editable by end users. The field can be hidden from the end users though, so this does come pretty close to meeting your criteria. 

Hope this is good news and if you have any more questions, I'd be glad to pass it along to them!

Greg Katechis can you put me in touch with that team? I would really appreciate it. I think this is a pretty glaring gap in the current SDK. 

Hi Seth...I sent this over to the team that handles this so any updates will be coming from them. Unfortunately, I don't have any additional info myself at this time, but they will see the update here. 

any update here Greg Katechis? a bit of a blocker for us from shipping to production right now

thanks for getting back to me Greg Katechis! based on the docs, the SDK, etc - I believe the intent of custom fields is to support this...however, the fact that the Zendesk API considers the authenticated mobile client SDK as a "customer" is what's causing the issue

the ideal/expected use case based off everything I've read from Zendesk could be: 

1. create custom field in zendesk dash 
2. make custom field private / only editable to admins 
3. let mobile SDKs send values for those fields 

could/should be that simple I think..I also know there used to be a private additional info field which of course would be nice too but custom fields is the papercut right now

Hi Seth! You are correct that there isn't a way to do this, however I did see that our SDK team is currently investigating use cases for this. I'll pass this along to them to see if they have any follow-up that they want to run by you.