You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Custom Menu Fields must have a Default Value selected?

Accepted answer
edited Sep 11, 2015 9:52PM in General Functional Discussions 12 comments


We recently ran into an apparent defect when adding a value to a custom field menu for the second time in almost two years. The change resulted in a value=0 error for the field that prevented incidents from flowing into the Service Cloud via the API. We were told by Support that this is a defect and that the workaround is to set a default value for the field to prevent it.

We have a lot of custom fields that are meant to be used in very specific situations that make up a small percentage of our incidents, so setting a default value for all of these is pretty impractical for us. So I'm wondering:

Howdy, Stranger!

Log In

To view full details, sign in.


Don't have an account? Click here to get started!