POST
|
Good Morning! Yes, that service does have upload capability that does indeed function. I see from re-reading my initial summary at the beginning that I'd left out specifically stating that the upload function works, simply implied it by the other statements. The back-end GP service I built does correctly and completely function if used manually or used within ArcMap, it's only the Geoprocessing Widget's "GPDataFile" input case where I'm having issues. Just as a reassurance, the direct-access to the GP service upload is via the usual trio of Upload Item/Register Item/Info at http://[redacted].net/arcgis/rest/services/Regional/KMLService/GPServer/uploads Alternatively, as is implied by your sample link, you have this same type of service generated. Is there a possibility that you can send me the structure you used for your GPservice, on the off chance that yours uses the KML to Layer tool differently? It would be strange but not impossible for me to have generated a working GP service which is nevertheless incompatible with the widget....
... View more
09-09-2014
06:49 AM
|
0
|
0
|
2117
|
POST
|
Thanks for the info, Mani...but it leaves me thoroughly confused regarding the following from the "Geoprocessing Widget Tags" reference at ArcGIS Viewer for Flex : <inputparams> The input parameters for the geoprocessing task. It has the following child tag: <param> The input parameter. It has the following attributes in addition to child tags: name—Name of the input parameters as defined on the server. Required. type—Type of parameter. Valid values are featurerecordset, string, boolean, long, double, date, linearunit, datafile, GPDataFile [added in version 3.2], rasterdatalayer [added in version 3.3], and multivalue:string. Required. Note: If working with the GPDataFile input type, a UI to upload file(s) displays. The GP service configured with the widget must support uploads. This functionality is provided beginning with ArcGIS 10.1. Above is the sequence I'm following with my use of the "GPDataFile" parameter type, which strongly implies that within the Geoprocessing Widget itself, there is supposedly a method for automatically accomplishing the back-end tasks you mentioned in your response. It's listed as available from version 3.2 of the Flex Viewer, and I'm using the 3.3 version. Is it that this is documented as available yet wasn't actually implemented in the Geoprocessing Widget, or is it that I'm using the advertised function incorrectly? I'd rather not have to build a completely different widget in order to achieve a result advertised as already existing, which is what I'd be doing by following your method. Thanks again for your assistance so far....
... View more
09-05-2014
12:09 PM
|
0
|
2
|
2117
|
POST
|
I'm tackling the concept of creating a local GP service to convert a /local/ KML file to a viewable layer, then viewing the output layer in Flex Viewer (3.3 in use.) I've currently got a GP service built and operating on our ArcGIS server, and it works correctly using ArcMap by way of accepting the input file and generating the output layer for display. I can also generate the correct result by manually browsing to and using the GPDataFile input of the service. If manually added, the resulting map service exists in the FV 3.3 instance. Long story short, I've got the back-end part of this working. What I'm looking for is a usage example for the ESRI Geoprocessing Widget, that uses the GPDataFile input parameter type. The widget tags reference simply shows the existence of the parameter, and mentions that it should generate a dialog for file upload when used - when I change the GeoprocessingWidget.xml file to include the requisite taskurl/helpurl and the inputparams block, I end up with a 1009 error (null object reference) while the widget tries to initialize. I don't get any dialog popup for selecting the source file. I've verified spelling & case on all the references, and a different GP service I created for another instance of the Geoprocessing Widget does work, so I know this is at least partially an error in how I'm configuring the XML. Here's a snippet showing how I'm configuring the input parameter: <inputparams> <param name="KMLInput" label="Input KML File" required="true" type="GPDataFile" visible="false"> </param> </inputparams> It's frustrating that the tag is referenced in the help, but there's not a usage example for it in the manner of the other input parameter types!
... View more
09-03-2014
12:38 PM
|
0
|
5
|
8073
|
POST
|
In the case of widgets provided as source, the config.xml file should be provided in the same folder as the <widget>.mxml file - you'll want to make whatever necessary edits to the config.xml file, then copy it to the same destination folder as your widget's .swf file. That /should/ solve the specific problem of the config.xml file not being found. Good luck with your coding!
... View more
04-17-2013
06:17 AM
|
0
|
0
|
232
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|