Latest Contributions by TimMinter

Well, not finding an edit button for that post.  2021 has arrived, Sparx EA 15.1 is installed and not up-to-date, and of course stuff has moved around.  Revised instructions: Sparx EA: Start > Preferences > Preferences > Objects > uncheck "Sort Features Alphabetically" Publish > Import > ArcGIS (add the workspace XML, schema only) double-click the "Workspace" object in the project browser to open a graphic view of your geodatabase schema find the disorderly table or feature class graphic right-click within the frame > Features > Attributes right-click the field that you want to be in a different order and choose "Move up" or "Move down" as pleases you Close the Features properties viewer Extensions > ArcGIS > Export ArcGIS Workspace XML Publish > Publish > ArcGIS > specify output XML filename and location > Export ... View more

Hi Alice - In my testing scenario, SQL Server is on a PM - Dell Precision 7530, i9, 32 GB RAM at 2933 MHz, 2 SSDs, which turns out to be pretty zappity and not prone to machinery-borne pokiness.  The Esri support case is still open, and seems to be moving toward bug status this morning after the tech was able to reproduce the problem.  A key finding at the moment is that when I write a view that delivers lat/long columns as SQL Server Spatial geography data type, the slowness occurs with ArcGIS Pro 2.6.3 and up.  All remains fast with ArcGIS Pro 2.6.2 and down and also with ArcMap 10.8.1 and down.  The problem does not currently seem to be about SQL Server, my SQL view writing skillz (which certainly could improve), or the device. cheers, tim ... View more

Update - well...  had to open a support case with Esri.  At present, it appears to be headed toward bug status.  Because a support request can consume significant customer staff time, I can share the case number in case you need to go down this path.  If it reaches bug status, I'll post a link, if possible. ... View more

Hmm.  Well, I just typed up a rather detailed "me too" note on this item which has gone poof.  The short of it is, "me too" with 2.6.3 and 2.7 in SQL Server 2016 eGDB 10.8.1.2.6.  Result - use 2.6.2 and don't spend time with support request. I was stepping back in to add that SQL Server Profiler shows ArcGIS Pro issuing this query: SELECT top 1 SHAPE FROM <view> WHERE SHAPE IS NOT NULL AND SHAPE.STIsValid() = 1 When I issue that query in SSMS, it takes 1m 1s to return one record out of 501 total that the view returns in less than 1s.  SQL Server Profiler indicates that ArcGIS Pro issues the query over and over and over and over again.  Might be a thing to look at. tim edit - it looks like my detailed post de-poofed.  great.   ... View more

Hi John, et al, We noticed this problem when we upgraded from ArcGIS Pro 2.6.2 to 2.6.3.  It remains a problem at 2.7.  We currently have a SQL Server 2016 (13.0.5102.14) database with a view that returns 501 records in less than a second (edit: in SSMS) with ObjectID, Shape (geography, null), and other columns.  ArcGIS Pro 2.6.2 could read and load the view in a few seconds.  ArcGIS Pro 2.6.3 and up cannot even get the properties for the view in less than 10 minutes.  Rather than expending noticeable resources with a support request, our strategy is generally to use ArcGIS Pro "whatever version works" for the particular function that we need to complete.  So, in this case, we just read our view with ArcGIS Pro 2.6.2. It would be great if Esri staff could notice this kind of discussion in the forum and handle bug evaluations internally rather than requiring Esri customers to spend significant amounts of our time to reproduce and enter into the bug log.  It would be even greater if all the testing harnesses and holistic quality approaches could catch these sorts of things. tim ... View more

Ok, I got back around to it.  I made a backup of an example database in my sandbox environment, then followed the guidance in the linked SQL Server documentation above to shrink it.  It dropped from ~188 GB to ~10 GB instantly.  It's a 10.8.1.2.6 enterprise geodatabase schema, so I added all content to an ArcGIS Pro 2.6.3 map and rendered it.  Some spot checks suggest it's working fine.  I did not get into any deeper testing that might reveal subtle problems, but I kind of don't expect any. Cheers, tim, OCIII ... View more

If the FBThumb / Kudo thingy is the new "vote this idea up" thingy, then I'm voting up... or thumbing or something.  Yes, please consider making it easy to export, delete, overwrite, edit, view, and redact confidential system information from metadata for all objects that support metadata. Edit - a little while later...  it turns out there is a Rube Goldberg (https://en.wikipedia.org/wiki/Rube_Goldberg_machine) approach to doing this.  Posting it here so I can find it again when the need arises. ArcGIS Pro > Project > Options > Geoprocessing > uncheck "Write geoprocessing operations to dataset metadata"    make a new feature class and import the fields from your original feature class, being sure to define the coordinate reference system the same.     Use the Append GP tool to load the records from your original feature class to your new feature class.  You turned off geoprocessing metadata logging, so it won't record in the metadata, hopefully. View the metadata for the original feature class, then "save as XML" (don't be tempted to export) like this:   I can't always reproduce the steps to get to that control.  Sometimes it appears, sometimes it doesn't.  Might be another idea...  anyway, import that metadata to your new feature class. Confirm that it all worked as you hoped. Done.  Whew. tim, Occasional Contributor III (my new Esri volunteer job title) ... View more

Hi Lisa, Nope, no progress.  I got all tangled up in COVID-19 support for our agency, and am only fully back to my day job now.  Actually, this item dropped through the cracks, and I need to get back around to it.  I think I have some kind of trashy databases lying around that I can test on without concern.  Thanks for the reminder .  I'll post my results here when I have some. tim ... View more

Hi Kory Kramer‌ I agree.  Please change the title to "ArcGIS Pro could maintain layer field order and alias when sharing web layer with time zone specified" if it has any chance of fitting and reset the status.  I don't think it's a niche idea.  I also think it fits squarely within the "Esri could provide an integrated, consistent, and reasonably good quality ArcGIS Platform" idea. Thanks, tim ... View more

I agree.  Thumb this up if you're willing - https://community.esri.com/ideas/17706  ... View more

Not in context of the ArcGIS Pro "Enable Editor Tracking" or ArcGIS Enterprise "Keep track of who created and last edited features" capabilities.  The field could have been named "TimTestDate" and my hypothesis is that it would have been shoved to the back of the list and renamed "timtestdate". The same thing happens when using the Convert Time Zone GP tool, so I hypothesize that the "share as web layer" function calls the GP tool, uses its code, or is similar in some other way. ... View more

Hi Kory, Well, bummer.  Nope, my idea remains quite valid in my opinion.  I found an ArcGIS Enterprise 8 environment that I could test with.  Getting into a little computer science here... hypothesis:  Kory is right and Tim is wrong test:  using WA-DNR's county boundaries (WA County Boundaries ) as the source feature class, import it to an ArcGIS Pro 2.5  file geodatabase, then share as web layer to an ArcGIS Enterprise 8 deployment.  Check the position and name of the date column before and after.  If the position and name of the date column has changed, then the hypothesis is disproven. results:  hypothesis is disproven ... View more

Hi Kory, How do we reset this idea to "not offered"?  Clue in bold italics... ArcGIS Pro 2.4.3 changes the field order when I "Share as Web Layer" and "Overwrite Web Layer" to an ArcGIS Enterprise 10.7.1 hosted feature layer.  Mostly, the end result are date fields ordered at the tail end of the field list with the field aliases stripped off.  This is truly annoying and causes duplicate work to monkey around with the pop-up field order and aliases. I upgraded to ArcGIS Pro 2.5, immediately smacked my head on this (BUG-000129031: In ArcGIS Pro 2.5, publishing a hosted feature layer.. ), used "language" out loud, and observed that ArcGIS Pro 2.5 continues to change field order for me when I don't want it to, and refuses to change field order for me when I do want it to (ArcGIS should allow the ability to permanently reorder fields in a table). How to reproduce:  make a file geodatabase feature class add a date column somewhere in the front of the column list share as web layer > Feature Layer > copy source data to AGE specify the time zone and daylight savings time publish to ArcGIS Enterprise 10.7.1. Ta-dah, ArcGIS Pro mangles the field order, alias, and column name. I notice that the Convert Time Zone GP tool offers the same results, so that's probably a clue for whoever didn't get the design principle message that ArcGIS does not change field order. Cheers, tim ... View more