Latest Contributions by Robert_LeClair

You can export a geodatabase feature class to a shapefile using the Feature Class to Shapefile GP tool.  The ObjectID field in a geodatabase feature class is an Esri created and maintained field and it cannot be deleted as you described.  When the feature class is exported to a shapefile, a comparable field is created called FID.  Again this is an Esri created and maintained field that cannot be deleted.   In some cases, you may have 64-bit field types in your geodatabase feature class.  These 64-bit field types are not supported in a 32-bit field type shapefile format.  You can read more about it here - Error: ArcGIS Pro: 002809 Field in is of an Unsupported Type for the Output Workspace ... View more

I don't think it's a license thing honestly.  A couple things to explore: Problem: ArcGIS World Geocoding Service Does Not Display in ArcGIS Pro How do I add Arcgis world geocoding service to Arc... - Esri Community Can't access World Geocoder Service in ArcGIS Pro - Esri Community ... View more

I think it's only the North American StreetMap Premium that requires the license.  If you're using the World Geocoding Service, then it will consume credits from one's ArcGIS online account.  You can learn about credits here - Understand credits—ArcGIS Online Help | Documentation - according to the documentation, it consumes 40 credits per 1000 addresses.  You can create your own address locator using a streets layer locally that will consume zero credits.  I've used the World Geocoding Service regularly and it does a great job address matching. ... View more

@AvaFarouche - there is a Tech Support paper on this error message here - Error: Invalid Locator: Cannot Use the Selected Locator for Batch Geocoding - maybe this will help resolve the issue? ... View more

Hi @JoeLummi - so I downloaded the *.aprx you uploaded and although I didn't have the data, I did see a "Failed to open table" warning message.  I clicked OK to clear the message and then closed all of the Map and Layout Views.  I then saved the *.aprx, closed ArcGIS Pro, and reopened the saved project.  I did not see any messages about "Failed to open map view" as they were all closed in the saved project.  I then opened each Map View individually and they all opened up albeit without any data.  Are you able to replicate this workflow?  If so, do you still see the warning message? ... View more

This appears to be BUG-000150061 - "Joining the raster layer to the table fails to populate the pop-ups on the joined layer of the classified raster."  Status is currently under review.  It was first seen in ArcGIS Pro 2.9.1.  ArcMap 10.8 does the same thing apparently. ... View more

Hi @JoeLummi - as I'm the only Esri person on this thread, it appears that the OP resolved their issue with creating a new project *.aprx - hence crickets I suppose. Question - are you experiencing the same issue as the OP? Please advise and I'll be more than happy to do so more deep diving on the question. To add to the thread and my next question to the OP - are you using ArcGIS Pro in conjunction with cloud storage devices?  If so, there's a tech support article discussing this - Problem: ArcGIS pro and Cloud Storage Services ... View more

Does the error/crash occur in a project that is saved to an *.aprx?  If so, can you test the Create Features workflow in a brand new, not saved project?   Does ArcGIS Pro still crash? ... View more

What coordinate system are you using?  Geographic or Projected?  If geographic, there was a BUG-000148600 - The 'Divide' tool does not work as expected when the map or data is in the geographic coordinate system."  This was fixed at 3.1.  And what release of ArcGIS Pro are you using? ... View more

Sorry to hear you're experiencing the spinning wheel of death.  I've been reviewing the internal support cases related to this issue and it did a similar case.  A user saw this issue when updating ArcGIS Pro from an earlier release, say 3.2.1 directly to 3.3.1 they saw this latency issue.  Steps the analyst took: "- We have tested the query on our end as well. When upgrading from version 3.2 to 3.3.1, there are two methods you can follow. If you choose to upgrade through the application, you can go to the "About" section under the project window. From there, you will see the latest version available with the patch. Clicking on the "Download Now" option will first download the main version, and then you can follow the same step to upgrade it to the latest patch. - On the other hand, if you prefer to upgrade the application through My Esri, you will need to download the main version first (in this case, version 3.3) and then install the patch. - Informed the user that It is important to note that installing the patch directly without downloading the main version first may cause performance issues in the application." So long story short, I'd recommend a clean uninstall of ArcGIS Pro and a clean install of the base ArcGIS Pro, say 3.3.0 or 3.4.0.  Then update the software patches and retest your workflow.  I know it's a not ideal scenario but from the case I'm reading, it does fix the spinning wheel of death. ... View more

I wonder if it's a corrupt *.aprx?  Can you create a new project, add a new map view, then add the layers in question and finally use the Apply Symbology from Layer workflow (in batch mode) to see if it works as expected? ... View more

Yay!  I'm glad it worked out for you @AnnaWall!  If you feel my answer was the solution, please click the "Accept as Solution" button below my answer to close out this thread.  Also, thank you for posting the idea as well!  This will allow others to upvote the idea and get some traction with the ArcGIS Pro Dev Team! ... View more

What release of ArcGIS Pro are you using?  There was BUG-000115328 - "Batch Apply Symbology From Layer only applies symbology to one layer in the list" but this was fixed at 2.3 ... View more

In ArcGIS Pro, background geoprocessing cannot be disabled as it is designed to run geoprocessing tasks in the background to allow you to continue working on other tasks. This is different from ArcMap, where you could choose to disable background geoprocessing. ... View more