POST
|
OK, that's a bummer. I knew it was a long shot once I noticed the compatibility note. It certainly creates a very narrow use case considering many data creators must share their databases and cannot guarantee the ESRI product or release the client is using. Are you saying work is underway to make feature classes and tables with contingent values at least readable by programs beyond ArcPro. such as ArcMap? This would be excellent news. Or development is only focused on use in apps such as Collector and ArcGIS Online?
... View more
02-28-2020
10:51 AM
|
0
|
0
|
1512
|
POST
|
Thank you for the response but my issue is that if I build a feature class with contingent values the feature class then becomes incompatible with ArcMap 10.7. I am hoping I have done something wrong because this creates a very narrow use case for the capability.
... View more
02-26-2020
03:01 PM
|
0
|
3
|
1512
|
POST
|
I am looking forward to contingent values and see it as a way to solve some of the editing complaints that I hear and hope to use the functionality as a carrot to move users to ArcPro but it has to not KILL my feature classes in ArcMap. I have a series of templates that I build for users. These templates have ArcMap 10.7 and ArcPro 2.4 options depending on the users preference. Both applications point to the same project file geodatabase. I built the contingencies and did some tests edits. LOVE the results and look forward to the rumored advancements in the functionality ( Planning for Contingencies – Contingent Values in ArcGIS Pro 2.4) . Unfortunately, when I open ArcMap the feature classes that now have contingent values, also, now have red exclamation marks. When I try to repair the data sources i get the attached message. " Error repairing the layer. The item does not have a definition. Unable to instantiatiate class for xml schema type: ArrayOfFieldGroup ". When I try to add them to a new .mxd I get a similar message. I found a small incompatibility note hidden in the documentation : Work with contingent values—Geodatabases | Documentation although it references Enterprise 10.7. Is there a plan to allow the formatting of contingent values for use in Pro that does not kill the feature classes' accessibility in ArcMap ?
... View more
02-24-2020
03:38 PM
|
1
|
5
|
1712
|
POST
|
I am looking forward to contingent values and see it as a way to solve some of the editing complaints that I hear and hope to use the functionality as a carrot to move users to ArcPro but it has to not KILL my feature classes in ArcMap. I have a series of templates that I build for users. These templates have ArcMap 10.7 and ArcPro 2.4 options depending on the users preference. Both applications point to the same project file geodatabase. I built the contingencies and did some tests edits. LOVE the results and look forward to the rumored advancements in the functionality. Unfortunately, when I open ArcMap the feature classes that have contingent values now have red exclamation marks and when I try to repair the data sources i get the attached message. I found the incompatibility note hidden in the documentation : Work with contingent values—Geodatabases | Documentation . Is there a plan to allow the formatting of contingent values for use in Pro that does not kill the feature classes' accessibility in ArcMap?
... View more
02-24-2020
03:29 PM
|
0
|
0
|
1043
|
POST
|
Hello Sean, I turned the map extent filter off in the screen shot to show that even without the filter only 6 errors display when there should be 2000+. A bit after posting this, I worked with ESRI Tech support on this for a couple weeks and it was reproducible on their end with their data. Unfortunately, it is a bug. In addition, it doe not appear ArcPro allows me to symbolize topological errors by type. I have decided to return to ArcMap to address this type work.
... View more
10-29-2019
09:20 AM
|
0
|
0
|
1068
|
POST
|
*** UPDATE*** as of 09/2019 below Issue has been logged as a bug. *** When using Error Inspector in ArcPro 2.3.3, it inconsistently filters errors to map extent in the error table. It seems that it will only filter results in the until an attribute table is opened. Once an attribute table is opened the error table will will not refresh and will display only the errors displayed at the time the attribute table was opened. This has become an issue when trying to filter by rule later so that I can edit specific types of errors in an extent as a batch. #goingbacktoArcMap Any ideas? Below is a quick run down of the process and screen shots to give an idea. I have tried this with different maps and data and get the same failure to refresh. Map Opened. Open Error Inspector Validate map on full extent 1) Filter by Map Extent is Active. 2) *2000 errors exist in the full map extent. Currently I am only worried about dangles along the quad border. I zoom into a location I want to inspect. 1) Filter by Map extent is active. 2) 6 Errors in map extent. Open Attribute Table. Zoom to full Extent. 1) Filter by map extent still active 2) Only 6 errors are listed 3) even after refreshing the table. If I zoom to a new location the table still does not refresh and will not properly populate this table until I have restarted the map project. It will function after restarting the program until I open an attribute table. After that the table fails to refresh.
... View more
08-07-2019
02:14 PM
|
0
|
2
|
1382
|
Title | Kudos | Posted |
---|---|---|
1 | 02-24-2020 03:38 PM |
Online Status |
Offline
|
Date Last Visited |
10-03-2023
01:02 AM
|