results return from the wrong layer, public version only

Permanently deleted user

November 28, 2013 03:48

I have a workflow that enables the user to select a parcel, buffer the parcel, and then returns all of the businesses that are within the buffer distance of that parcel.  They are two separate polygon layers.

It works fine on the internal site.  I copied the workflow to the public site, added the necessary proxy urls and changed the server name.  For the most part it works on the public site, except instead of selecting businesses at the end, it selects parcels.  It seems to think it is selecting businesses (the table is entitled businesses, not parcels) but the results are from the parcels data.

What am I missing, here?  Why would it work internally but then show results from the wrong layer externally?

0

• 

  Tom Neer

  November 28, 2013 04:04

  Are you using a referenced site or a duplicate site? There is a bug in the Select Features that won't return features correctly from a referenced site service. This will be fixed in the next release. This does not occur with duplicated/copied sites.

  0
• 

  Permanently deleted user

  November 28, 2013 05:19

  As far as I understand it is not a referenced site nor a duplicate site.  I built it on a different server, on a separate installation of Essentials.

  0
• 

  Permanently deleted user

  November 28, 2013 05:44

  Stephanie,

  It is not easy to find out the cause without to see the configuration of WF in Site.xml and WF itself.

  But I would check few things for the troubleshooting:

  (1) Open the Workflow file on WF Desinger - Find out 'SelectFeaturs' activity to check where the FeatureSet input is built, and to check if Map Service ID and LayerID(ofName) configuration are all what you expected. I would add one LOG activity to write it down to the logging file too. For the FeatureSet, you can use 'GetAttributeValues' to write it down what content of the FeatureSet is before SelectFeatures activity too.

  To check the input FeatureSet content, you may use 'FeatureSet to DataTable' and 'DataTable to csv', then write csv to the Log. If the FeatureSet content is different between your internal site and the public site, then find out where this FeatureSet comes from.

  (2)You may check Fiddler to check the server side to check if FeatureSet comes from the BufferTask (as Results) or QueryTask by adding the following insde <system.net> to Web.config on the REST: 

  <defaultProxy>

   

        <proxy proxyaddress="http://localhost:8888" bypassonlocal="False"/>

   

  </defaultProxy>

  M.

  0
• 

  Permanently deleted user

  November 28, 2013 06:37

  Hi Stephanie,

   

   just to expand on Munhwan's point on Fiddler, we have two knowledge base articles on how to get it setup. See:

  https://support.geocortex.com/use-fiddler-to-capture-web-traffic-between-a-web-browser-and-a-web-site

  and

  https://support.geocortex.com/use-fiddler-as-a-proxy

   

  regards,

  Edmond

   

  0
• 

  Nico Burgerhart

  November 28, 2013 17:16

  To see FeatureSet contents, you can also use yourfeaturesetvariable.ToJson

  0
• 

  Permanently deleted user

  November 30, 2013 03:47

  For anyone wondering, the problem was related to dynamic layers.  I have a sequence in the workflow to get around issues with dynamic layers (wherein if the layer is dynamic, instead of returning the url as http://server/arcgis/rest/services/MapName/MapServer/26  (or whatever your layer id is) it returns http://server/arcgis/rest/services/MapName/MapServer/dynamiclayer).  To cut a long story short, I put in a LayerSource variable for each layer that returns the actual layer id instead of dynamiclayer, and I had missed one!  It was using the ParcelLayerSource instead of the BusinessLayerSource.

  Thanks to Alejandro in support for helping me narrow that down.

  0

Please sign in to leave a comment.