Latest Contributions by RichardDaniels

I added an idea to have a more granular approach to the AI Assistance based on the app (Survey123 vs. Experience Builder vs. StoryMaps), currently it is All or nothing.  ... View more

inconsequential means ArcGIS Pro 3.1. and 3.2 will not run without .Net Desktop Runtime 6.0.x. It ignores, does not use, .Net 8. ... View more

NO, you must have .Net Desktop Runtime 6.0.5 or later (in the .Net 6 family) loaded on your computer with ArcGIS Pro 3.1 and 3.2. ArcGIS Pro 3.3 was a breaking change when they moved to .Net Desktop Runtime 8.  ... View more

This is the first I've heard about a CTRL-C or Right-click >Copy Bug in ArcGIS Pro 3.5, is there a Bug # for that one? ... View more

As a start I would check the shapefile location you are trying to create or save results to. Is it on your local machine (NOT in OneDrive), Do you have full r/w/modify permissions to the folder, Is the folder path 'shallow' (e.g., C:\Temp\Results\myshape file), I would also consider saving the results to a file geodatabase vs. a shapefile. Last, if you are saving datetime fields recall that a new datetime format was introduce with Pro 3.4 that is not supported in shapefiles. ... View more

After some checking, it looks like the 'AddInContent' Build Action for icons (or png files) in Pro AddIn is now just 'Content'.     Of note, in your config.daml you have the 'stub path' to the icon in the Image tag like so: <Image>Images\diamond_blue_32bit.png</Image>    If your icon is still not showing, then add the .\images folder to your Add-In file structure and add the icons or pngs you want to display. ... View more

If you are in Windows 10 or 11 just set File Explorer to show hidden files. [cid:image001.png@01DBE999.DD0EE2D0] ... View more

Several Service Packs were just released for ArcGIS Pro 3.3, 3.4. and 3.5 that addressed a BUG where 'locks' on geodatabases were not being removed. This may be causing your issue. To test, have you tried giving the output FC a different name, then renaming the FC afterwords. ... View more

example of a .prj file contents for WGS 1984.   GEOGCS["GCS_WGS_1984", DATUM["D_WGS_1984", SPHEROID["WGS_1984",6378137.0,298.257223563]], PRIMEM["Greenwich",0.0], UNIT["Degree",0.0174532925199433], AUTHORITY["EPSG",4326]] ... View more

ESRI just released SP 6 for ArcGIS Pro 3.3, it has several bug fixes related to 'ArcGIS Pro grays out when...'. Recommend you give it a try. ... View more

Define Projection is not the same as the Project Command. The fact the development team does not know this is problematic for a GIS software company. This needs to be escalated and ALSO submitted as an 'Idea' for new development. Having a Define Projection Tool within ArcGIS Pro that does not actually allow you to define a project is by its very nature a BUG. Failure of their design team to understand GIS workflows should not be a reason to refuse to implement a basic feature of ArcInfo, ArcView, ArcGIS Desktop, and ArcGIS Pro. Geographic data is provided by many organizations without proper supporting projection files (i.e. prj files). This often happens during GPS data collection and integration with other providers such as multiband raster data, AutoCad and Bentley Products. That is why Define Project exists. ... View more

If we are talking about a classic ArcSDE type of Geodatabase that lives on a server, defining the projection details is part of creating the database itself. AFTER the database is created one loads or adds Feature Classes and tables to the database. Perhaps that is the issue here, you are talking geodatabase creation vs. Feature Class? Workflow could be create empty Geodatabase with the desired end-state parameters, then prepare your feature classes as desired then import or do a Project command with the Geodatabase as the output folder to transform the FC's into the desired projection definition.  ... View more

If the ArcGIS Pro version is in General Availability phase, then all significant bugs should be addressed per Esri Product Life Cycle Policy dated January 2025. A field calculation error that can result in data corruption is a big deal and will be addressed in all versions of the application currently under support. In this case this error (BUG-000176644) was introduced with ArcGIS Pro 3.5 and addressed with SP 1. the error does not exist in ArcGIS Pro 3.3 or 3.4. Software patches or hot fixes o Provided to customers to resolve significant issues discovered in the product release. • New environment certification o When a major new version of an environment is released during the General Availability phase of an Esri product, Esri will test this new environment with the Esri software product in its General Availability phase and provide updated system requirements. ... View more

In Visual Studio 2022 check the properties for the file in your Solution Explorer. Should look like this:   ... View more