topic Re: Why won't Pro sort on Global ID? in ArcGIS Pro Questions

Why won't Pro sort on Global ID?

ThomasColson — Sun, 14 Oct 2018 19:49:56 GMT

So in troubleshooting this:

I can in Arc Map do this:

Which gets me to the offending row, from which I can figure out what is wrong with an attribute or geometry that's causing the issue. From there I can make a decision to delete the feature, go under the hood in SQL to edit something, edit it in SDE, or create a local copy. Take home message is, via the feature service, I can sort on GlobalID.

In Pro...cannot sort GlobalID from a feature service. I can from a .geodatabase or a feature class, both of which take time and more mouse clicks to bring into a map but not a feature service. Is there a valid reason why this capability was removed?

Re: Why won't Pro sort on Global ID?

JonathanFarmer_oldaccount — Mon, 15 Oct 2018 16:42:59 GMT

Hi Tom,

I just tested this on my end with Pro 2.2.3 and I can sort both ascending and descending using the GlobalID field on a feature service.

What happens when you try to? An error? Or is the option grayed out?

Jonathan

Re: Why won't Pro sort on Global ID?

ThomasColson — Mon, 15 Oct 2018 18:24:06 GMT

Data source is SQL 2014 ENT, Geography Storage Type, no SQL triggers or alteration to GlobalID default (Should be a class 4 GUID?), 10.6.1 feature service. Doesn't sort as a feature service, sorts as a .geodatabase.....

Re: Why won't Pro sort on Global ID?

MichaelVolz — Mon, 15 Oct 2018 18:42:12 GMT

Is the feature class registered with SDE or is it a query layer from a SQL 2014 database that is spatially enabled but not registered with SDE?

Re: Why won't Pro sort on Global ID?

JonathanFarmer_oldaccount — Mon, 15 Oct 2018 18:54:23 GMT

What version of Pro is this Tom? Because all my specs match yours except I'm running SQL 2016.

Re: Why won't Pro sort on Global ID?

ThomasColson — Tue, 22 Jun 2021 08:43:21 GMT

2.2.1, plain-vanilla SDE feature class, not a view, not a query. Everything in this workflow is out of the box. We have not certified 2.2.3 for use (security and regression testing), and likely won't any time soon. I should add, being off-line capable, the feature class is archived, but not registered as versioned. Editor tracking. Storage type geography, GCS NAD83. Here is a public copy of one of the FC's that's not sorting, but the GlobalID's will be different: http://www.arcgis.com/home/item.html?id=2d413fce1dc349bd92af8fdcdbe8c3c9

Sure wish there was a GUID validator in Pro...https://community.esri.com/ideas/14489 . I have had mixes of different types of GUID's cause GIS processes to fail in the past.

Re: Why won't Pro sort on Global ID?

JonathanFarmer_oldaccount — Mon, 15 Oct 2018 21:12:30 GMT

Tom,

I just took the URL for this data and added it to Pro. In both 2.2.3 and 2.2.1 on my end, it will sort by GlobalID both ascending and descending.

If I sort ascending, I get:

{a8cc2e69-4148-4ae9-9861-00594bbaa163}

If I sort descending, I get:

{064308cd-9f49-4cf1-bb9c-ff4b299139e9}

It is hard to tell from the gif exactly what you see on your end but I take it these results aren't it?

Jonathan

Re: Why won't Pro sort on Global ID?

ThomasColson — Tue, 16 Oct 2018 12:14:50 GMT

Nope, the AGOL Feature Service, as well as the Server 10.6.1 Feature service, does not sort on GlobalID. Happens with 100% of my feature services, on multiple installs of 2.2.1. We may be defining "Sort" differently (Alberto Ferrari : How are GUIDs sorted by SQL Server? ). When the feature service is online, I get the same results you do. When I download it to a .geodatabase, I get:

And:

Note how the sorting is occurring on

 0 1 2 3  4 5  6 7  8 9  A B C D E F

Re: Why won't Pro sort on Global ID?

ThomasColson — Tue, 16 Oct 2018 12:52:33 GMT

...and looking at the AGOL version of the data I posted, I can sort the GlobalID in Arc Map, as in the two images above, without having to take it offline. Interestingly, in both Pro and Arc, when online, the feature service Globalids are rendered in lower case, when offline....upper case, however, Pro is missing the Arc Map functionality to be able to sort the GlobalID while online.

GUID switch to lower case

Guid feature type, uppercase by default on FGDB?

GUID case in ArcGIS Pro

https://community.esri.com/thread/115041

Re: Why won't Pro sort on Global ID?

JonathanFarmer_oldaccount — Tue, 16 Oct 2018 16:33:27 GMT

Thanks for the additional information Tom. I see the issue now. When you stated things weren't sorting, I figured they weren't sorting at all. But the behavior is different in Pro when online vs. off compared to ArcMap.

I see what you do. Let me look into this some more and I can get back with you.

Jonathan

Re: Why won't Pro sort on Global ID?

JonathanFarmer_oldaccount — Tue, 16 Oct 2018 17:12:37 GMT

Tom,

Well I thought I could reproduce this but now I'm not so sure.

ArcMap, both online and offline and Pro, offline, sort like this:

Ascending: {E13D9E6D-06CC-4CCF-9BC6-0011D61A3DDB}

Descending: {66595284-1337-4B3C-B315-FEE424F42CF0}

You can see that it is starting its sort with the last set of numbers (0011D61A3DDB vs. FEE424F42CF0).

But I still see that same sorting behavior with Pro online as well. We are still sorting by that last section.

It is hard to see from the GIF exactly what is happening on your end. Can you attach a video to this thread so I can take a closer look at the differences between Pro online and offline on your end?

Jonathan

Re: Why won't Pro sort on Global ID?

ThomasColson — Tue, 16 Oct 2018 18:28:33 GMT

(view in My Videos)

Re: Why won't Pro sort on Global ID?

JonathanFarmer_oldaccount — Tue, 16 Oct 2018 21:39:59 GMT

Hi Tom,

OK, I see what you do in the video but I want to make sure all the scenarios match up.

When I am working with a feature service or data coming from an enterprise geodatabase, either in ArcMap or ArcGIS Pro, I see that we sort the GlobalID fields by the last set of characters.

Ascending: {E13D9E6D-06CC-4CCF-9BC6-0011D61A3DDB}

Descending: {66595284-1337-4B3C-B315-FEE424F42CF0}

However, when working with a mobile geodatabase, we sort that same GlobalID field by the first set of characters. We also sort this way for a file geodatabase.

Ascending:

{091A6365-E29F-487A-A063-3376D024AF24}

Descending:

{898F25E2-5740-450E-8E04-1441F3F51ECC}

I see this same behavior in both Desktop clients and at different versions of each so it does look like this is expected. But from what you are telling me, you see ArcMap sort feature services and enterprise geodatabases by the first set of characters and not the last? If that is the case it may need a Support case because that isn't what you should see based on testing this here.

Jonathan

Re: Why won't Pro sort on Global ID?

ThomasColson — Wed, 17 Oct 2018 11:26:19 GMT

Hmmmmm...if I call TS...it will get "fixed", and I no longer will be able to sort using the first octet in Arc Map....

Let's look at a work around: There's something wrong with GlobalID {09BE107D-DF2B-4FAB-A24E-02F464EDA029} according to the server logs. That's all the info I get. Not ObjectID, not primary display field, nothing. In Arc Map, I can sort the feature service and easily find {09BE107D-DF2B-4FAB-A24E-02F464EDA029}. Neither in Arcmap or Pro can the Find (Locate) tool be used to search on GlobalID. Interestingly enough, in this particular data, I have another GUID attribute that DOES work in the Locate tool.

So in Pro, how does one find {09BE107D-DF2B-4FAB-A24E-02F464EDA029}?

Re: Why won't Pro sort on Global ID?

JonathanFarmer_oldaccount — Wed, 17 Oct 2018 18:06:52 GMT

Hi Tom,

I'm going to create a Support case for you to log a bug for this Locate issue. You are correct, the Locate tool will not find a GlobalID value even though that field is listed as a choice when setting up the layer. That's a bug.

As a workaround, use Select By Attributes. It will allow you to choose that particular GlobalID value and then find it in the table and on the map for you. This works for me.

I'll reach out shortly from the case.

Jonathan

Re: Why won't Pro sort on Global ID?

ThomasColson — Wed, 17 Oct 2018 19:32:57 GMT

The outcome of this is to fall back to "Select by Attributes" if you're truly needing to find a row by GlobalID, and you're encountering BUG-000117511 Locate Tool in ArcGIS Pro Gives Users the Option to Search Based on GlobalID Field But Returns No Results.