I was told to make a feature request for this bug by one of your customer service reps. Here are the details: Allow an API user to retrieve values on a custom field that contains commas or colons. Currently these characters are special characters that delimit fields or custom fields. There is no way to escape/encode these characters to allow an API call to successfully retrieve their value even though the UI allows these characters to be used as part of a custom field name.
The following call will fail due to the commas in the custom field name, even though the custom field name is allowed in Workfront:
https://mydomain.workfront.com/attask/api/v5.0/TASK/595f22b45654d98536c5a66b5a9302?apiKey=myapikey&f... this item tie into any other existing, current, or future item?