POST
|
I was abled to add custom LODs using the MapView 'constraint' property. The LODs[] can be autocast using JSON similar to what is found for lod property in the REST API for a basemap service. https://developers.arcgis.com/javascript/latest/api-reference/esri-views-MapView.html#constraints view.constraints = { lods: [ { level: 0, resolution: 156543.03392800014, scale: 5.91657527591555E8 }, { level: 1, resolution: 78271.51696399994, scale: 2.95828763795777E8 } ...... ]};
... View more
11-13-2020
02:43 PM
|
0
|
0
|
1003
|
POST
|
Well, I spoke too soon. The first time I reopened the new Pro project and ran it again the same crash on the first Field Calculate after the first Join.
... View more
08-24-2018
02:36 PM
|
0
|
4
|
319
|
POST
|
Thanks to all for the feedback. I just started over in a new project, and rebuilt the task and have not had problem since. Will try to follow up with ESRI tho and get this logged as a Bug. I have had some feedback from others offline where this has happened to them.
... View more
08-24-2018
02:18 PM
|
0
|
0
|
1172
|
POST
|
Yes I sent every error report to ESRI, they should have about 30 or so by now.
... View more
08-24-2018
02:17 PM
|
0
|
0
|
1172
|
POST
|
Yes, joined the offending target table to a table in the same geodatabse and had the same issue. Any process that target table partipates in is now causing problems. Its almost like a ghost lock is on the table.
... View more
08-24-2018
02:16 PM
|
0
|
0
|
1172
|
POST
|
The fields names are the same, but I am using the table qualifier ![tablename].[fieldname]! in the dialog because of the join. Some additional info from further testing: 1. The Feature Class is created during a configured Task using the Feature Class to Feature Class geoprocessing tool. Joining and calculating always crashes on that output feature class like explained above. Copying that output in the same geodatabase and running a join and calculate on the copied feature class does not crash Pro. 2. If I manually run the Feature Class to Feature Class to create the output, the crash does not occur. 3. I have tried pausing the Map drawing, and turning off all layers and the problem still persists. Has anyone seen a configured Task become corrupt? It seems to me that something about the Task is interfering with that feature class. Even when the task is not running and after restarting Pro.
... View more
08-22-2018
03:09 PM
|
0
|
5
|
1172
|
POST
|
At version 2.2.1, I am having consistent issues running the Field Calculator on a feature class joined to a geodatabase table. These two objects are based within two separate file geodatabases. The Field Calculation is simple, setting the value of a text field equal to the value of another text field from the joined table. The Field Calculation completes, and then ArcGIS Pro crashes. It appears that the map tries to refresh after the Calculation and that is when ArcGIS Pro crashes. When I open the project again, the changes to the field have persisted. This crash happens every time no matter whether I run the Field Calculator from the Attribute table, from within a configured Task, or from the Data Management toolbox. There are null values in the field basing the Join. So I have also tried unchecking "Keep All Target Features" so the calculation would theoretically skip those. Any troubleshooting tips would be helpful.
... View more
08-22-2018
12:56 PM
|
0
|
14
|
1976
|
Online Status |
Offline
|
Date Last Visited |
06-03-2021
01:01 PM
|