Example of 'Query Layer' specifying statistics?

Permanently deleted user

10 octobre 2017 22:52

Would like to make a query to get max & mins to give the user a more accurate range of input values...

 

Below is an example for objectid, if you use the arcgis server query page, you can specify the following in Output Statistics,

 

[{"statisticType":"min","onStatisticField":"objectid", "outStatisticFieldName":"MinID"},

{"statisticType":"max","onStatisticField":"objectid", "outStatisticFieldName":"MaxID"}]

 

 

Is this possible in the 'Query Layer' activity, i think the JSON might be causing problems...

0

• 

  Permanently deleted user

  20 octobre 2017 15:34

  Hi Ryan,

   

  Following your question, we did some investigation and found that this is a bug. We'll work on fixing this for a future update. Thanks for asking about it!

  0
• 

  Permanently deleted user

  6 septembre 2018 08:44

  Is this still a bug? What is bug number?

  0
• 

  Permanently deleted user

  10 septembre 2018 17:19

  Hello,

   

  This was being tracked as BUG 12239 and it is now fixed and released.

   

  Regards,

   

  Wayne Richard

  Latitude Geographics Group Ltd.

  Head Office: 300 – 1117 Wharf Street Victoria, BC Canada V8W 1T7

  Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com 

  Developers of Geocortex web-based mapping software | www.geocortex.com

  An Esri Platinum Business Partner

   

  0
• 

  Belinda Kerr

  10 septembre 2018 23:10

  Thats great new Wayne. I can't find any reference to that bug number in any of the release notes. Which version contained the fix??

  0
• 

  Permanently deleted user

  10 septembre 2018 23:20

  Hi Belinda,

   

  It is marked as fixed for version 5.2. If you scroll down to 5.2 and click the "The update also addresses these" link, you should see it.

   

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

   

  Please let me know if you are still seeing the issue.

   

  Regards,

   

  Wayne

  0
• 

  Belinda Kerr

  10 septembre 2018 23:37

  Hi Wayne,

   

  In that case, yes we are still getting the issue. The statistics fails if we do it via workflow. As a workaround we build the exact same request and send it as a web request and it works. I had AAM here helping me to do it and that was their workaround.

   

  Belinda?

  0
• 

  Permanently deleted user

  11 septembre 2018 15:00

  OK, thanks Belinda, I have re-opened the issue.

  0
• 

  Permanently deleted user

  4 décembre 2018 14:50

  Wayne,

   

  Is this stil an issue? I get an error when determining max value

  0
• 

  Permanently deleted user

  4 décembre 2018 16:18

  Hi Erik,

   

  What are you using for the "Out Statistics" property?

   

  Regards,

   

  Wayne

  0
• 

  Permanently deleted user

  6 décembre 2018 00:20

  Hi Erik,

   

  I did a quick check in case I could set up a workflow that reproduces the issue in the latest version, but I was still able to get the max value. See attached, and if you could share your broken one with us (or at least the "Out Statistics" property), that ought to help

  0
• 

  Permanently deleted user

  6 décembre 2018 03:42

  Amanda,

   

  I tried your suggestion with succes. The part I was missing was the outStatisticFieldName. This is not neccesary when using the rest endpoint. My workaround was the webrequest and this also does not need this parameter. Thanks a lot.

  0

Vous devez vous connecter pour laisser un commentaire.