nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why do GUID fields display as Text?

EricMahaffey1

I'm currently trying to work with some tables within SQL Server that have GUID fields. I'm running ArcGIS Desktop 10.3.1 and pulling the data through a standard database connection. When I look at the table properties within ArcCatalog the GUID fields are listed as Data Type: GUID. However, when I load them into ArcMap, they show as data type: String. This is causing problems when I then try to join the query layer to another table in the database that has a matching foreign key field (that is GUID as well). Any thoughts on this?

I also notice that when I add DB Spatial Views to ArcMap I have to identify a unique identifier field in the query layer. However, a table does not require this. The tables have indexed fields, so this might be the reason, but wanted to be sure. This might be a separate topic than above though.

Find more posts tagged with

Accepted answers

TinaMorgan1

Since these are database tables, could they create a database view that joins the tables together in the database, then use the view as a query layer in ArcMap? I wonder if this may remove some of the clunkiness...

Also, Esri GUID fields are associated with SQL Server uniqueidentifier data types. You can see how to create uniqueidentifier columns in SQL Server...

uniqueidentifier (Transact-SQL) | Microsoft Docs

"A column or local variable of uniqueidentifier data type can be initialized to a value in the following ways:+

By using the NEWID or NEWSEQUENTIALID functions.
By converting from a string constant in the form xyz-xyz-xyz-xyz-xyz, in which each x is a hexadecimal digit in the range 0-9 or a-f. For example, 6F9619FF-8B86-D011-B42D-00C04FC964FF is a valid uniqueidentifier value."

Per the second method, where it mentions converting strings...could this be a part of the underlying issue?

How were your two tables originally created?

All comments

EricMahaffey1

Thanks Tina. We ended up using the same solution that you mentioned. We created a series of DB Views to get around the field type issue with joining. Once that was done, it didn't matter how ArcMap perceived the field types.

TinaMorgan1

Also, Esri GUID fields are associated with SQL Server uniqueidentifier data types. You can see how to create uniqueidentifier columns in SQL Server...

uniqueidentifier (Transact-SQL) | Microsoft Docs

"A column or local variable of uniqueidentifier data type can be initialized to a value in the following ways:+

By using the NEWID or NEWSEQUENTIALID functions.
By converting from a string constant in the form xyz-xyz-xyz-xyz-xyz, in which each x is a hexadecimal digit in the range 0-9 or a-f. For example, 6F9619FF-8B86-D011-B42D-00C04FC964FF is a valid uniqueidentifier value."

Per the second method, where it mentions converting strings...could this be a part of the underlying issue?

How were your two tables originally created?

EricMahaffey1

Do both table's fields get converted to Text and that is why the join succeeds? Yes, I believe that's what's happening. They don't get converted until the view is added to ArcMap as a Query Layer.

What is the version of the enterprise geodatabase (sde)? The enterprise geodatabase is SQL Server Enterprise Edition (64-bit) version 10.50.6220 SP3

Are both tables registered with the geodatabase? No. We are using the SQL Server geometry data type. I wish I could register them, however, our DB is structured without the use of SDE

Anonymous User

So what I've noticed is if I add both tables to ArcMap, the join will succeed.

Do both table's fields get converted to Text and that is why the join succeeds?

It seems weird that the field is getting converted to a text field in ArcMap when it is a GUID.

What is the version of the enterprise geodatabase (sde)?
Are both tables registered with the geodatabase?

EricMahaffey1

Thanks Supriya. So what I've noticed is if I add both tables to ArcMap, the join will succeed. However, if I add only one table and try to join to a table through a database connection, I cannot select the field that I need to join with from the second table. The list of available fields is reduced, and each of those fields are Type:Text. Hopefully this workflow description makes sense.

Anonymous User

Hi Eric,

Thanks for your post.

This is causing problems when I then try to join the query layer to another table in the database that has a matching foreign key field (that is GUID as well).

When you add this other table into ArcMap does the GUID field remain GUID and not get switched to string?

I did a quick test:

Added a GUID field to a table
Added the table to ArcMap
In the attribute table check the field data type, its still GUID

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.