AnsweredAssumed Answered

using geoprocessor via javascript API v3

Question asked by charlie.elverson on Nov 13, 2018
Latest reply on Nov 13, 2018 by charlie.elverson

I have a geoprocessor service that's published using server 10.4. I know that it's setup properly because a web app builder widget is able to successfully communicate with it (using JavaScriptAPI v4, I believe). However, I'm unable to get results from it with a JavaScript API v3 application.

 

My coworker setup synchronous and asynchronous versions of the geoprocessor service. So, I've tried using the geoprocessor's execute() and submitJob() methods. Both have ultimately returned "esriJobSucceeded" statuses, however when I try to retrieve the data the features array is empty.

 

Here's the result I get:

 

  1. {paramName: "out_table", dataType: "GPRecordSet", value: {…}, _ssl: undefined}
    1. dataType: "GPRecordSet"
    2. paramName: "out_table"
    3. value:
      1. displayFieldName: ""
      2. exceededTransferLimit: false
      3. features: []
      4. fields: (10) [{…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}, {…}]
      5. geometryType: undefined
      6. spatialReference: {}
      7. transform: null
      8. __proto__: Object
    4. _ssl: undefined
    5. __proto__: Object

 

Has anyone run into something similar before? Maybe the server needs extra configuration to allow communication between geoprocessor services and API v3? Do server versions 10.4 and later not support JS API v3?

Outcomes