How can I CalculateField_Management a field that has a Domain based schema?

John_Spence

I'm having a DOH! moment here am can't seem to pull myself out of the nosedive.  Converting my scripts using arcpy.CalculateField_management from VB to Python and ran into a small hiccup.

Using VB, this is what I did:

arcpy.CalculateField_management(combinedOutFC + '__ATTACH_vw', 'REL_GLOBALID', '[DBName."Domain\!UserSchema".FC_Publish.GlobalID]')

But in Python, that is not cool so I did this:

arcpy.CalculateField_management(combinedOutFC + '__ATTACH_vw', 'REL_GLOBALID', '!GlobalID!', 'PYTHON_9.3'

Here is the caveat:

Prior to this I performed a join:  

arcpy.AddJoin_management(combinedOutFC + "__ATTACH_vw", "REL_GLOBALID", combinedOutFC, "GUIDCopy")

Where I am going wrong with:

arcpy.CalculateField_management(combinedOutFC + '__ATTACH_vw', 'REL_GLOBALID', '!GlobalID!', 'PYTHON_9.3'

Thanks ahead of time for what I know will be "oh yeah" moment of the day for me.    Thank you all for your help over the years.

Oh!!!  Error is looking like this:

error encountered.ERROR 000539: Invalid field FeatureClass.GlobalID
Failed to execute (CalculateField).
PYTHON ERRORS:
Traceback info:
File "Publish.py", line 182, in <module>
arcpy.CalculateField_management(combinedOutFC + '__ATTACH_vw', 'REL_GLOBALID', '!' + combinedOutFC + '.GlobalID!', 'PYTHON_9.3')

Error Info:
ERROR 000539: Invalid field FeatureClass.GlobalID
Failed to execute (CalculateField).
Closing Log File and Exiting Process.

curtvprice

Your error dump messages do not match your code.

I suspect you need a prefix and "." to access the GlobalID field in the related table, especially when there are unusual paths to access the data sources.  Although a usually helpful way to find the syntax is to use Describe to use the name property to get the prefix. Note my use of Python .format() -- much easier when the syntax gets weird to keep things straight!

tbl <SPAN class="operator token">=</SPAN> <SPAN class="string token">"{}__ATTACH_vw"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>combinedOutFC<SPAN class="punctuation token">)</SPAN>
expr <SPAN class="operator token">=</SPAN> <SPAN class="string token">"!{}.GlobalID!"</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>arcpy<SPAN class="punctuation token">.</SPAN>Describe<SPAN class="punctuation token">(</SPAN>tbl<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">.</SPAN>name<SPAN class="punctuation token">)</SPAN>‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

this doesn't always work, specially when working with SDE joins, raster tables, etc. In these cases sometimes I need to resort to printing a debug message with the field names so I can see what syntax Python is looking for to access the joined field:

<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">[</SPAN>f<SPAN class="punctuation token">.</SPAN>name <SPAN class="keyword token">for</SPAN> f <SPAN class="keyword token">in</SPAN> arcpy<SPAN class="punctuation token">.</SPAN>ListFields<SPAN class="punctuation token">(</SPAN>tbl<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">)</SPAN>‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN></SPAN>