Latest Contributions by RonaldVanderpool

Yes, that is exactly what the issue is.  It doesn't matter if I am in the Catalog view or pane, when I select Design/Fields for any feature class and the above image is the reference, I cannot change the order of the fields. I get a slashed circle when attempting to drag field to the new position. Above the fields were added at a later date than feature class creation and it would be nice to have the PIPE_CLASS & PRESSURE_CLASS right under the PIPE_SIZE. This is really only a convenience matter most specifically so in Collector the field workers do not have to scroll to the field and I do not have to rearrange in the pop-up. I typically fix as I develop a new geodatabase (copy) from an existing blank geodatabase by just opening each copied layer and moving the fields before I populate the feature class. Would like to just fix the blank geodatabase instead of recreation or having to do what I describe above. ... View more

Greetings Jimmy. The only change we made on our end for field workers was to remove the Android Collector Beta and use the old Android Collector. I was confident that we were safe until Carl had his issues on an iOS. Fingers are crossed around here because the support was not what I expected, very similar to what you experienced. Too many versions of Android and iOS operating systems out there and if units are not updated regularly then who knows. Also if they are updated and the Collector app is not set to interface with the new OS versions then there we go again. Scary business, but it is about Halloween so scary is expected..........HaHaHa ... View more

Hi Carl. We have not had it happen on the iOS devices and have not seen the error for a few months in Android. I would suggest taking a screenshot of the error and run it up the ESRI support flagpole and see if they have had any luck on their end. Also post the same in this dialog but not under comments to me rather the original post by Emily. That way the ESRI GeoNet monitors may see it better. I have a feeling that it is a device OS issue and not something in Collector. Too many versions of iOS and Android for Collector to have to associate with may be the root. ... View more

Hi Andrew, No resolutions for you. Sorry. Just wanted you and GeoNet to know that I have had similar issues with the Field Calculator. It happens just as you say, either with Python or Arcade, and also whether I am calculating a field in an AGOL feature or one that is on my desktop. Saving the project and then restarting Pro sometimes fixes the issue and on more than one occasion I have to restart my PC to get Pro functionality working.  Sigh.........At least that restarting has got me back working. Not sure if it is a bug but starting to maybe sound like it. ... View more

Thanks! ... View more

Seems to me that it is a function that should be there. Using the zoom to verify that all of my fields are as needed is not very intuitive. Not sure if it qualifies as a bug but should be included in the software code. ... View more

Very interesting Victoria! It does show up with data in the table. I was trying to review an empty database for continuity of fields before I started populating features. Good to know! Thanks! Seems a little strange that it is not available for a blank database as it is in ArcCatalog. Thanks again! ... View more

Thanks Kory! Good information. Gotta love collaboration. ... View more

Aha! Add my main data folder to Catalog and there they are. Do most users just save a Project and use it to review data as opposed to adding a folder every time research is needed? User choice I presume. Thanks Kory! and thanks for your quick guidance! ... View more

Ahhh. Thanks Kory. What about random shapefiles that are floating outside of the gdb environment? ... View more

Also not happening on our iOS devices using the new Collector. Hoping the issue silently goes away when the beta evolves to the real deal. And soon would be better.  Any ideas ESRI when the beta will turn? ... View more

I guess my biggest concern, well over being restricted in field use, is that it is not a consistent error and cannot be re-created for analysis. I have no idea what could be causing this in the geodatabase. I believe that it stems from some Collector vs. OS issue more than anything else. We have another error when downloading maps in Collector Classic for Android. ESRI has that case but have never found any corrections. We started downloading smaller area maps with far less detail and have not had the issue re-occur since. Still waiting on the new Android Collector to get out of beta status so we can utilize the functionality of the offline map areas, but I digress as that is another story. Good luck Jimmy! ... View more