Why can't I use Show Results in webappbuilder on a self created FeatureSet

Erik Kuipers

5. April 2018 06:56

I used a GP service and process the json results to a new featureSet. When I want to Use Show Results i get an error. When I use the same WF in Html5 Viewer it gives me back the correct results. My simple wf can be found on https://esrinederland.maps.arcgis.com/home/item.html?id=98c3b208798a412e99870cf65de77754.

It is real simple but I think webappbuilder needs a layer in the webmap?

I use an older version of webappbuilder. I tried using a newer version but had other problems (december release)

0

• 

  Stefan Schweigert

  5. April 2018 15:19

  Hi Erik,

   

  I'm not able to load your workflow but there are differences in how the Show Results uses the Map Service Id, Layer Id, and Layer Name inputs. Take a look at the GW5 - Show Results sample workflow. In order for the layer to be highlighted in WAB, use the Layer Name input and make sure that the spatial reference from the previous query matches the map's spatial reference.

   

  Note that our next release will contain detailed information about how to properly configure the Show Results activity in both applications.

   

  Thanks, Stefan

  0
• 

  Erik Kuipers

  5. April 2018 15:27

  Stefan,

   

  I shared the wf. The problem is that I cannot provide a MapServiceId, LayerId because the data is comming from a webservice(Gp tool) and has no corresponding layer/featureclass in a arcgis rest endpoint or webapp. When I query a existing mapservice it is no problem but I create a featureset from scratch (with or without geometry). Then you get an error. You can check the wf now so I'm curious what the reason is.

  0
• 

  Permanently deleted user

  5. April 2018 23:26

  Hi Erik,

   

  Thanks for raising the issue and providing the workflow. It looks like there is a bug with Show Results in WAB where it does not work when fields aren't defined on the featureset. This means that Show Results also fails when you try to use a Graphic[] or Graphic for the Features property. I believe that this was working in some previous versions, as we had addressed a similar issue with using a Graphic[] object in the past.

   

  I found that applying a fields property to your manually created featureset, and then using =$featureSet1.featureSet instead of =$featureSet1.featureSet.features worked as a workaround. I've attached my test modified from your workflow, and we'll bring this up with our developers.

  0
• 

  Permanently deleted user

  19. Juni 2018 19:05

  Just thought I'd follow up to note that the issue should be fixed now. It's listed on the release notes for 5.5.1 under "issues" as 17974

  https://docs.geocortex.com/workflow/latest/help/Default.htm#wf5/help/release-notes.htm

  0

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