Latest Contributions by AllenDailey1

My idea is for ArcGIS Pro to display a warning message when the user opens Fields view either via a layer in the layer list or via the catalog.  The message would say something to the effect that field configurations for a layer and field configurations for a feature class (like in Catalog) are unrelated.  Maybe use wording like what is used in documentation on this page:  https://pro.arcgis.com/en/pro-app/latest/help/data/geodatabases/overview/create-modify-and-delete-fields.htm Here is a screenshot of the part I'm referring to: I have been using Pro for a long time, but I only learned this just today, the hard way.  I put a lot of time into configuring aliases and data types (e.g. I specified that a numeric field should be percentage with only one decimal place) for a layer.  I need to use this data in a different file geodatabase and aprx (for this project, I have sort of "dev" and "prod" aprx's and file geodatabases).  It was only after I had copied the feature class to the new geodatabase and tried to configure symbology in the new map that I discovered that none of my field configurations were there.  I did a lot of troubleshooting to try to figure out what happened.  I did online research and eventually found the above documentation.  So I guess I have to do all that work over again.  That's super frustrating.  I feel like the part that I shared a screenshot of, above, should be way higher up on that documentation page!  It's almost near the bottom.  How is anyone going to know about it? I really wish that field configurations/aliases were not disconnected between a layer and the source feature class.  I have no use for this scenario, myself, and I feel honestly sad that if I were to do further tidying-up of fields in a feature class (source data) in the future, the changes would not carry through to a map I'm already using the layer in.   Anyway, if this functionality stays in Pro, it would be EXTREMELY helpful to make it more apparent to users.  Thanks for reading.   ... View more

I shared a feature class and a file geodatabase table to my Enterprise Portal as a web layer.  I need to have both the feature class and the table in a web map.  When I make a map with the new Map Viewer, the table is nowhere to be found.  But when I use Map Viewer Classic, the table is in the map, just like I need.  But I need to use the new Map Viewer because Map Viewer Classic is of course obsolete. I did confirm that both the feature class and the standalone table are listed in the map service's REST endpoint. There's no editing involved - no versioning, no feature service, etc. I am the owner of the web layer / service.  And I am working on the web maps as myself, the same account that is the owner. I'm using ArcGIS Pro 3.0.3 Enterprise 10.9.1 build 28388 My organization cannot upgrade to Enterprise 11 yet.  In fact, the work I am trying to do with this web layer is part of our work to get all our map services running from Pro, as part of our preparation for upgrading.  So I have to get this work done before we can upgrade. I did see something on Esri Community from 2 years ago about related tables not showing up in the new map viewer, like Esri hadn't built this functionality yet.  I don't know if this is related. A crazy thing is that on another Enterprise Portal we have (the Dev one), an essentially identical web layer with a table DOES show up in the new map viewer.  That Portal has the exact same version and build as the one I'm having the problem with (which is our Production portal), and the services have the same settings.  I don't see how the new map viewer could be acting differently in the two Portals, but it is. Does anyone know how to get the table to show up in Map Viewer?  Is it a bug? ... View more