POST
|
We have a need to use the Living Atlas Terrain Layer in a Web Tool to analyze slope and aspect within a boundary. The overall model/scripts are rather complex, but the issue I have is simple. To use the Terrain Image Service I have tried creating a GIS Server connnection and providing the url for the Living Atlas Server. This used to work, but now the Living Atlas Terrain3D layer does not validate. However, the TopoBathy3D layer does. Is there a credential issue going on because the Terrain is also registered with Portal? I've been experimenting with different data sources for the Living Atlas Terrain Layer by using the item registered with Portal, but that always fails to publish, siting an error with credentials. Is using the Terrain layer supported in a Web Tool? What is the recommended approach for using it? Should we register the Living Atlas layers with Portal, or does the web tool need to connect directly to AGOL?
... View more
2 weeks ago
|
0
|
0
|
26
|
POST
|
With ArcPro 2.6.3 I am publishing a Web Tool that contains multiple results. I've been doing this for several months without issue, but now when it publishes it is displaying the wrong GUI. There are three Results being published. In the GUI, when I open the first tool I see the GUI for the third tool. And when I open the third tool I see the GUI for the first. Now each time I publish after creating a new sharing session, it is doing the same thing. It seems like something is wrong with the service definition, but I haven't the foggiest how to fix it. When I look at the Web Tool on the server machine it is built this way (with the wrong GUI), so I think Pro is packaging it incorrectly. Any ideas?
... View more
3 weeks ago
|
0
|
0
|
40
|
IDEA
|
Hello Korey and Tim, I ran into this issue today and will follow your steps to reorder Fields in Pro and republish. What I am doing is joining a table to a feature class to create a target schema with empty join fields then publishing to Pro 10.8.1. I am using the fields aliases from the hosted layer to match to the field aliases after converting Excel to Table and updating the hosted layer with the records from the table. If I understand correctly, simply reordering the fields in Pro will do some magic and they will publish correctly? Is this a documented bug that can be fixed in Pro?
... View more
12-02-2020
02:13 PM
|
0
|
0
|
138
|
POST
|
Follow Up-- When a toolbox is accidently deleted from the file network by one user via a Pro Project, and I have that same toolbox open in my Project, I can continue to work with the tools, Yay. However, the toolbox does not exist in File Explorer or Catalog since it was deleted. Scary and sorry for anyone else who needs them! Why are 'Remove' and 'Delete' adjacent to each other in the right click options on a Toolbox in a Pro Project. Many people will accidently delete the toolbox. When I create a new toolbox with the same name in the same folder, it is automagically populated with the previous script tools and models. Wow! and How! I feel like I just got lucky because I still had my Project open. Can Esri point me to some documentation on the intended behavior and just how best we are supposed to manage this caching in Pro Projects? Today it actually helped me for the first time, but it usually just overwrites my updates which I need to learn how to avoid. Our organization is migrating to Pro and I need to know the answers to these questions to safely implement the software. Does this involve the incremental Project backups that seem to occur and prompt me when opening a previously crashed project? Are Project Backups the key to how Pro can work from an Enterprise File Share? How do Catalog items in Pro get updated from the file network and when do the updates made in a Project get reflected back to the file share? Is this entire Caching behavior something that is in flux and constantly changing with updates to Pro, so much so that we may have to modify how we work? Again, I really just need to know what is going on behind the scenes so I can provide recommendation for others using the software in our organization and our clients'.
... View more
09-24-2020
10:57 AM
|
1
|
0
|
81
|
POST
|
Hello, I've had a lot of weird issues with ArcPro caching old versions of script and models which are making development and service publishing very difficult. Here is the most recent example. I have a toolbox named with _dev and toolbox named _JP. I am needing to replace the _dev toolbox with the _JP toolbox so I delete the _dev toolbox, Copy the _JP toolbox and paste it into the folder. When I inspect the model in the pasted toolbox it looks correct. If I rename the toolbox to _dev and then open the model, it reverts back to the version that I deleted! This naming issue seems to also exist on the GIS Server when deleting and republishing a GP Service with the same name, but that's a different issue (maybe?) This has got to be a bug in Pro, or an issue with the network share. Either way I need help to resolve this issue because it makes Pro very difficult to use for developing GP Services and toolboxes. For the longest time my GP Services never worked because older versions were getting published instead and they were broken. Perhaps there is an ArcPro Settings Option to disable deleted file caching? Or is this a behavior caused by the Network File share? I'd be happy to work with someone at Esri to fix these issues in Pro. Thanks!
... View more
09-23-2020
07:02 AM
|
0
|
1
|
107
|
POST
|
In ArcPro I've created script tools and models that use the interactive feature input. Sometimes it works, and the layer is added to the map for users to create features. However, most of the time when clicking the edit button to create a feature, it goes gray then absolutely nothing happens in the map. I do see that the feature class is created in the project's default gdb, but it is not getting added to the open map. Does anyone know a fix for this, other than writing arcpy.mp python code to add the layer to the map (I don't really see that as an option here anyway for interactive feature input).
... View more
09-22-2020
01:19 PM
|
0
|
0
|
31
|
POST
|
Hello, We've migrated a rather large ArcMap Model to ArcPro and are wanting to have it published as a Web Tool to Portal 10.7.1 and 10.8 (dev). The 10.7.1 Server already has ArcMap GP Service published to it that have existed for a long time and the Web Tools don't run successfully once published. I am thinking there could be an issue with the python environment on the server. Reading the documentation on 10.8, Deploying custom Python packages for ArcGIS Server—ArcGIS Server | Documentation for ArcGIS Enterprise, it states that At ArcGIS Enterprise 10.5 and later, a Python 3-based conda environment is included with ArcGIS Server . Starting at ArcGIS Server 10.7.1, you can specify a Python environment for all geoprocessing services. Starting at ArcGIS Server 10.8.1, you can specify a Python environment for a single geoprocessing service. To help troubleshoot our issues with publishing Web Tools to 10.7.I have a question: Out of the box, is it supported to be able to run ArcMap GP Services and ArcPro WebTool/GP Services on one server, or do all the services have to use one environment until 10.8.1? Thanks!!
... View more
07-27-2020
07:09 AM
|
0
|
0
|
46
|
POST
|
Hi, When publishing a Web Tool from ArcPro 2.5.1, I often times get no response when clicking on the Publish button after first Analyzing the result. What I see is that an .sddraft is being generated without a local toolbox OnPremisePath in the resources of the sddraft. How can I ensure that the OnPremisePath in the sddraft gets populated and the Web Tool successfully stages and publishes? Successfull Publish sddraft Resource section: < Resources xsi: type = ' typens:ArrayOfSVCResource ' > < SVCResource xsi: type = ' typens:SVCResource ' > < ID > xxxxxxx-xxxxxx-xxxxxx-xxxxxx </ ID > < Name > clippedsources.xml </ Name > < OnPremisePath > C:\Users\xxxxxxx\AppData\Local\Temp\ArcGISProTemp25188\FEMAFloodZoneA.tbx </ OnPremisePath > < StagingPath > </ StagingPath > < ServerPath > </ ServerPath > < InPackagePath > </ InPackagePath > < OnServerName > </ OnServerName > < ClientName > xxxx-xxxxx </ ClientName > < CIMPath > CIMPATH=clippedsources/clippedsources.xml </ CIMPath > < RepositoryID > 0 </ RepositoryID > </ SVCResource > </ Resources > UnSuccessfull Publish sddraft Resource section: < Resources xsi: type = ' typens:ArrayOfSVCResource ' > < SVCResource xsi: type = ' typens:SVCResource ' > < ID > xxxxxx-xxxxxx-xxxxxxx-xxxx </ ID > < Name > clippedsources.xml </ Name > < OnPremisePath > </ OnPremisePath > < StagingPath > </ StagingPath > < ServerPath > </ ServerPath > < InPackagePath > </ InPackagePath > < OnServerName > </ OnServerName > < ClientName > xxxx-xxxxx </ ClientName > < CIMPath > CIMPATH=clippedsources/clippedsources.xml </ CIMPath > < RepositoryID > 0 </ RepositoryID > </ SVCResource > </ Resources >
... View more
07-24-2020
07:41 AM
|
0
|
0
|
73
|
POST
|
Hi, In ArcPro 2.5.1 when publishing a Web Tool, I can be successful. However, sometimes when I am working on publishing multiple tools during testing of a larger model, I run into this issue. The 'Confirm Sharing Change' Dialog is empty. If I click Yes, The 'Share As Web Tool' Pane Opens and a spinning wheel appears, never to go away. At this point I restart ArcPro. Any ideas what could be causing this?
... View more
07-24-2020
06:10 AM
|
0
|
0
|
34
|
POST
|
Hi Dan, Could you describe why using a script tool vs toolbox tool would not work? Do you think it is because of what is going on inside the script tool rather than just that it is a script tool? I was thinking this type of issue is related to multiprocessing task bug within Esri tools, but that could be wrong. Thanks!
... View more
06-17-2020
12:42 PM
|
0
|
1
|
37
|
Online Status |
Offline
|
Date Last Visited |
2 weeks ago
|