I use IntelliJ with Jetforcer for Salesforce development. Starting yesterday, I began receiving the following error when trying to retrieve Standard sObjects for my project:

jsonNot a valid enumeration for type: class com.sforce.soap.partner.SoapType

I've had no troubles retrieving other component types and have been unable to find a resolution to this issue. What would be a reason why I am seeing this error for Standard sObjects?

  • Which object does it cause the issue for?
    – dmachop
    May 10, 2019 at 15:16
  • @dmachop It has the same error for any Standard object I try to retrieve; also the Custom objects seem to retrieve fine. May 10, 2019 at 16:32
  • Let's take an example here. If it fails for Account object, can you see from your workbench what the field definitions are and which one has the soapType = 'json'?
    – dmachop
    May 10, 2019 at 17:36
  • @dmachop That's the weird thing, when I open workbench none of the fields have a json soapType. Also, when open the .object file in an IntelliJ window -> Right Click -> 'Retrieve Account.object' it works fine. But when I open the Salesforce tab -> 'Retrieve Project...' -> Select Account object that is when I get the error. May 10, 2019 at 18:15
  • Looks like a bug. Report to Salesforce.
    – dmachop
    May 10, 2019 at 18:17

3 Answers 3


This issue was fixed in JetForcer 2.0.15



Since API 46, there is a new FieldType json. You can see an example of standard object using this field type on the field "RecordData" from object "ApiEvent": https://developer.salesforce.com/docs/atlas.en-us.220.0.api.meta/api/sforce_api_objects_apievent.htm?search_text=ApiEvent

Jetforcer must be using an outdated force-wsc (version >46.0.0) package but trying to get the sObjects from a preview org using API 46.

You should report this bug to Salesforce.


After raising this as a bug with Salesforce there is know a known issue around the problems that v46 introduced when the Real-Time Event Monitoring Beta is enabled.

Known Issue W-6222075: DescribeSObject call using the v45.0 Partner API are failing due to a complex type(json) that isn't defined in the WSDL

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .