POST
|
Brian, I just tested this with ArcGIS Pro 2.3.2 and ArcMap 10.7 and I don't see the behavior there. You mentioned you don't either with 2.3.2 so it seems that it's been addressed. However, we do not have a defect on this issue that I can find so I'm not sure if this was something on our end that we just fixed or something odd happening on your end. Do you know the ArcGIS Pro version(s) where you were seeing the behavior? Was it specific to a version of ArcMap as well or not? Jonathan
... View more
05-01-2019
07:55 AM
|
0
|
5
|
676
|
POST
|
Hi Mitch, I too am unable to find a way to change the arrow / line color. If no one else replies with an answer for you, I would recommend contacting Tech Support so that they can log an enhancement for this issue and we can consider it for a future release. Jonathan
... View more
04-30-2019
08:01 AM
|
1
|
0
|
1355
|
POST
|
Hi Patrick, I'll echo what Randall said, there isn't a reason in this case that you HAVE to use Data Store if you don't want to. it's certainly an option but it sounds like you prefer to edit referenced data in your Enterprise DBMS. If your primary concern is permissions for each municipality, there are a few ways you could set things up so that each municipality can only edit their own data. You could have each municipality be the owner of their own services. Allowed operations on services apply to publishers and users only so admins and service owners can perform all operations. https://enterprise.arcgis.com/en/server/latest/publish-services/windows/editor-permissions-for-feature-services.htm You could possibly use ownership based access control: https://enterprise.arcgis.com/en/server/latest/publish-services/windows/ownership-based-access-control-for-feature-services.htm You could publish different services based on different child versions. This is more work for you to manage since it adds geodatabase complexity and management requirements but it's something to consider at least. Hope that gives you ideas. Jonathan
... View more
04-30-2019
07:44 AM
|
0
|
0
|
381
|
POST
|
Public URL for the defect is now available if you all would like to subscribe to it: https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEyMTE2MA==
... View more
04-10-2019
02:05 PM
|
0
|
0
|
888
|
POST
|
Hi all, I wanted to let everyone know that we do have a bug logged for this issue: BUG-000121160: When selecting a row within an attribute table to change the value for a specific attribute field, the error message, "Update table row. Value doesn't fall within Domain" is returned. We don't have a public link on the support.esri.com site at the moment but we are aware of the issue and if you do need to be attached to the bug for tracking purposes, please contact Technical Support so they can get you added on. Thanks everyone for letting us know about this issue! Jonathan
... View more
04-10-2019
07:24 AM
|
0
|
2
|
888
|
POST
|
Hi, Is this issue specific to file geodatabases on shared file servers? Do they see the same behavior with data coming from a local drive? When they see the error opening the attribute table, are they able to do anything in the map? Pan, zoom, etc? Does the data in the map refresh? It sounds like a lost connection to the data which is why I ask. My last question would be, do multiple people in the organization see this issue using the same data from the same shared file server? Or is this related to 1 instance of Pro? Jonathan
... View more
04-08-2019
07:51 AM
|
0
|
4
|
589
|
POST
|
Chip, SQL Server requirements for 10.3.x below. These pages are for both Desktop and Server. With 10.3.1, you are fine with SP1. But that is a problem with using mixed releases of things, what is supported with one version is not always supported with another. That being said, SP3 will work fine with Server 10.3.1 as well. Microsoft SQL Server database requirements for ArcGIS 10.3.x—Help | ArcGIS Desktop To setup an SDE Intercept, you can follow the article below. How To: Set up an SDEINTERCEPT log file on a client machine for ArcGIS Desktop and ArcGIS Server You will follow the workflow for Desktop and not Server since we are working with Pro and an Enterprise geodatabase within Pro. Once setup, you can open Pro and proceed with the workflow until you get the error. The database trace needs to be done by someone with access to the database backend. I presume that is your IT department? This documentation below from Microsoft goes into how to set that up. Create a Trace (SQL Server Profiler) - SQL Server | Microsoft Docs Just have them check off the "User Error Message" and "Exception" parameters when setting it up. Also, as always, feel free to log a case with Support if you feel like you could use a little more hands on help here. They know these troubleshooting tools well and can assist on a screen share with setting things up and interpreting them. Jonathan
... View more
03-11-2019
02:58 PM
|
0
|
1
|
1152
|
POST
|
Mervyn, Kory and I got together and we've decided to log a defect for this behavior. BUG-000120695: Intersection Snapping Not Locating Vertexes in Multi-Part Polygon in ArcGIS Pro Something is definitely off there between Pro and ArcMap. Do you want to be attached to this defect? If so, let me know and I can do that. Thanks for working with us on this and let me know if you have any questions. cc Kory Kramer
... View more
03-11-2019
02:44 PM
|
1
|
1
|
1437
|
POST
|
Unfortunately not. It's something that is being looked at for a future release per my understanding but I don't have any information on the latest there.
... View more
03-11-2019
10:55 AM
|
1
|
1
|
770
|
POST
|
Hi Chip, You are running SQL Server 2012 with Service Pack 1. If you want to decipher those build numbers, I've always found this site to be helpful: SQL Server build numbers | Build Numbers The issue here is that the minimum supported environment at 10.5.x is SQL Server 2012 with Service Pack 3. ArcMap may be a bit more forgiving than Pro. Regardless if this is the issue here or not, you'll need to upgrade ASAP. Microsoft SQL Server database requirements for ArcGIS 10.5.x—System Requirements | ArcGIS Desktop As far as the replication goes, you are talking about geodatabase replication correct? Not SQL Server replication? Having a geodatabase replica in place shouldn't cause these issues, I'm not aware of any problems there. I think you'll need to setup and run an SDE Intercept and trace from Pro when you try to edit the data and get that error. It may help narrow down where the problem is occurring. Have you worked with intercepts and traces before? Jonathan
... View more
03-11-2019
09:32 AM
|
0
|
3
|
1152
|
POST
|
Hi, This is a limitation of the web scene viewer, done for performance reasons. However, you might consider doing a scene service as a way to move forward. Scene services—Documentation | ArcGIS Enterprise Jonathan
... View more
03-11-2019
09:09 AM
|
1
|
3
|
770
|
POST
|
Hi Mervyn, I just tested this with Pro 2.3.1 and I am able to snap to an intersection of 2 polygons in the same layer without issue. Could this be a tolerance issue in your snapping settings possibly? If I set my XY tolerance really low (like 1 pixel), I see issues with Pro not wanting to snap to the intersection. If I set it to a very high level (like 100 pixels), it almost snaps automatically without moving the mouse. Something to check out at least. Jonathan
... View more
03-11-2019
07:50 AM
|
1
|
7
|
1151
|
POST
|
Hi Chip, With a 10.3.1 geodatabase, you may be running into compatibility issues between your Pro version and the DBMS version. What version is your SQL Server instance? I'd recommend you be at 2012 SP3 at least. If this is happening with multiple versions of Pro on multiple machines, I'd lean against something to do with a specific install. Whatever this is appears to be a larger issue. Jonathan
... View more
03-11-2019
07:41 AM
|
1
|
5
|
1152
|
POST
|
Thanks Marcos. Can you log a case with Technical Support on this? I'd like to get this issue in our system so we have a record of it. I haven't been able to reproduce the exact behavior you are seeing in Pro 2.3 but I have seen the same error when trying to place a new feature rather than updating an attribute in a field. I'll keep working with that on my end and see what comes out of that. Jonathan
... View more
02-20-2019
03:55 PM
|
1
|
1
|
1070
|
POST
|
Hey Tom. I don't have an answer as to why but I do see the same behavior on my end. Give it some time, there may be someone who replies here with the answer. But, if not, feel free to reach out to Support so they can log the issue and decide how best to move forward here. Jonathan
... View more
02-20-2019
07:46 AM
|
2
|
0
|
429
|
Title | Kudos | Posted |
---|---|---|
1 | 08-10-2018 07:40 AM | |
1 | 04-12-2018 01:47 PM | |
1 | 01-04-2019 07:43 AM | |
1 | 10-03-2018 07:12 AM | |
1 | 01-03-2019 07:56 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|