Latest Contributions by JoshuaBixby

The views that can't be deleted from ArcGIS Pro can be deleted from any SQLite tool just fine.  They can't be deleted in ArcGIS Pro because they are created in SQLite but not populated in various GDB system tables, so the delete tools can't really figure out what to do.  The solution to the delete issue is to have them never created in SQLite in the first place if the SQL is invalid. ... View more

The answer lies mostly in the intro paragraph for each tool.  Underlining is my emphasis. From Make Table View (Data Management)—ArcGIS Pro | Documentation Creates a table view from an input table or feature class.... From Make Query Table (Data Management)—ArcGIS Pro | Documentation Applies an SQL query to a database, and the results are represented in either a layer or table view. The query can be used to join several tables or return a subset of fields or rows from the original data in the database. Make Table View supports a broader range of data sources and is much more efficient because it is a one-to-one tool, i.e., one table per table view.  Make Query Table allows for joining tables, but that expanded functionality comes at the cost of fewer supported data sources and less performance for simple cases. ... View more

George, I have seen several examples where ArcGIS 10.8.2 contains ArcGIS 10.9.1 code, and it appears that includes tools that create enterprise geodatabases as well. ... View more

I ended up creating two lists, one for the actual multiprocessing pool and a second with metadata I created and populated about the jobs I put into the pool.  One of the items I tracked in the metadata pool was the start time of when the job was submitted to the pool.  As I looped over the pool to retrieve results, I would check the jobs that were still running and see when their start time was, and I would calculate elapsed time.  If a running job passed a designated elapsed time, I would issue a terminate command.  I would also use the metadata pool list to check whether an existing process had crashed by keeping a list of PIDs.  If a process had crashed, I would print a warning. ... View more

Christian, thanks for the updates.  Here's hoping "later this year" is more like summer than 12/31/2022. 🙂 ... View more

You can't pass an Arcade operator, &&, in a SQL statement because whatever is processing the SQL has no clue how to handle &&. ... View more

Beyond Python 2 to Python 3, ArcGIS Pro also involved going from 32-bit to 64-bit.  Are you sure you have the proper database drivers installed since you are trying to access an enterprise geodatabase?   ... View more

QGIS handles the same situation by having actual NULL italicized and light-grey.   ... View more

这篇文章似乎是重复的  标注放置重叠在一起无法调节！没有令人满意的设置方案！ - Esri Community.  如有重复请删除。 ... View more

@ChristianWells , you seem to understand the support and defect processes well, so maybe you can have some influence on the following.  It would be great if the URLs for bugs and defects were decipherable from knowing the bug or defect.  For example, BUG-000094271 has a URL of support.esri.com/en/bugs/nimbus/QlVHLTAwMDA5NDI3MQ== .  Whatever the rhyme or reason is behind turning "BUG-000094271" into "QlVHLTAwMDA5NDI3MQ==" isn't documented anywhere.  For an organization with tens of thousands of GIS users that logs 50-100 defects and enhancements a year, linking internal documentation to Esri Support documentation is a very manual process.  It would be nice if one could determine the URL by knowing the BUG or ENH number. Update:  For My Esri, both the old/classic UI and the new UI support URLs that are derived directly from bug or enhancement numbers.  For BUG-000094271 and the My Esri classic UI, the URL is:  my.esri.com/classic/#/support/bugs/BUG-000094271 ... View more

Managing the email separate from AGOL and My Esri, that seems less than ideal.  I will wait to see if anyone from the EC team has any additional comments before e-mailing them directly. ... View more