Latest Contributions by JamesShively

Using the geoprocessing tool, "Layer To KML" within a python script tool and ArcGIS Pro v2.9.2 crashes without warning, or error(s). If the tool is used outside of the script tool, there is no problem and KMZ is created as expected. No screen shots available but my code is as follows: arcpy.LayerToKML_conversion(out_layer, "MergedShape.kmz") Seems straight forward enough but crashes everytime. ... View more

Data Aggregation Widget returns message, "Error saving features". Hosted feature layer settings: Editing Enable Editing Enable Sync What kind of editing is allowed? Add Delete Update:       Attributes and geometry What features can editors see? Editors can see all features. What features can editors edit? Editors can edit all features. ... View more

When I run the "Share as web tool" the following message pops-up after clicking the Publish button: "Successfully published web tool...". However, the tool does not appear in the location specified or anywhere else for that matter. Upon clicking the link at the bottom, "Manage the web tool", there is only a small, blank box that appears as though there should be a link in it, but there is not. Connection to portal is good. All boxes are completed with options chosen. With the message of a successful publication and no error messages present, I am unable to troubleshoot any particular section as why the tool does not actually publish. Has anyone else experienced this issue and more importantly, were you able to figure out, remedy the problem, and publish the web tool? Thanks in advance. ... View more

Add support in a widget (geoprocessing service) for the use of 'type Field'  (FC attributes) from selected input features. The geoprocessing service published to Portal creates a wedge-shaped polygon extending out from a point feature class and uses three separate fields with two numeric values for wedge edge and a textual field for the extent of the wedge: 1) Direction degree of 1st edge of wedge (e.g., 42); 2) Direction degree of 2nd edge of wedge (e.g., 65) and; 3) Distance from point feature of the extent of the wedge (e.g., 15 NAUTICALMILES). This geoprocessing service will be run on multiple point features and so requires the capability of the service to read values from a field and not a simple, manual input from the user. ... View more

I have created a map with pop-ups showing a limited set of attributes for point features. This map was then inserted into a dashboard. The pop-ups in the web map are fine and show the attributes I selected before publishing. However, when the point features are selected/clicked on in the map within the dashboard, the pop-ups show no content with only a message that reads, "No Content". Why? More importantly, how do I fix this to show pop-ups the same as the pop-ups in the web map? ... View more