Zum Hauptinhalt gehen

Geometry Picker workflow in Workflow 5 fails on WKID being Undefined

Kommentare

3 Kommentare

  • Permanently deleted user

    Did you ever resolve this issue? I'm having the same problem. I thought it was fixed by adding a Project Geometry activity between the Geometry Picker and Query activities, but it doesn't work if there are multiple geometries. Single geometry works.

    The input for the Project activity is =$formGeoPicker.state.geometryPicker1.value.geometry

    and I defined an output spatial reference (102100).

    The input for the Query activity is

    =$projectGeometry1.results (this is how multiple geometries get passed) It doesn't matter if I specify an output spatial reference or not, still fails.

    I can see the geometries in the log, but it fails on the Query activity with Cannot read property 'wkid' of undefined.

    Anyone?

    0
  • Permanently deleted user

    I am having the same issue. The geometry is already defined as 102100, so I do not see why we would need to reproject it.

    0
  • Sean McClurkan

    I think this is a"workaround" that Amanda sent me. If you take the Geometry Picker result and use it in a Create Feature activity:

     

    Create Feature - [id queryGeometryFeature]

    Geometry =$formSearch.state.geometryPicker1.value.geometry[0]

     

    The you can put the feature geometry in a variable:

    =$queryGeometry.result =$queryGeometryFeature.feature.geometry

     

    Then use the geometry variable in your Query task.

     

    I put my geometry into a variable because I may be getting my geometry from multiple places, but you could use the feature geometry directly in the Query Task. Basically, everything loves a feature. Values and results from other activities, not so much.

     

     

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.