topic Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4 in ArcGIS Utility Network Questions

Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

BryanMay531 — Thu, 29 Feb 2024 19:48:24 GMT

Can anyone remind me how identify the field? :

f_7864070e49f14ae5a76a09237e7e2ed4

there is somewhere to crossreference to a real field name but I can't find it today

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

RobertKrisher — Thu, 29 Feb 2024 19:59:38 GMT

The target field column in your data mapping sheet should be the literal field name (e.g. TargetField), the expression column should be a python expression to evaluate to your value (e.g. !SOURCEFIELD!). Check out this tutorial (https://learn.arcgis.com/en/projects/load-data-into-the-arcgis-utility-network/) for the basics of data mappings, along with a few more advanced scenarios like value lookups.

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

BryanMay531 — Thu, 29 Feb 2024 20:13:58 GMT

I'mjust trying to figure out what that temp field name relates to in my data. Here is the mapping page in my WS

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

RobertKrisher — Thu, 29 Feb 2024 20:38:26 GMT

@BryanMay531 I'm not sure actually, but my guess would be one of the fields that is using the EmptyStringtoNull method. Can you post the snippet for that method? I suspect it is returning something other than the Python representation of null (None).

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

BryanMay531 — Thu, 29 Feb 2024 20:42:47 GMT

Sure. I attached the script.

thanks

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

PierreloupDucroix — Thu, 29 Feb 2024 20:42:52 GMT

Each time I wrote a custom python function in the base.py script and referenced this function in the Mapping sheet, I had this behavior. The name of the field in error logs is not the original name, but something like f_7864070e49f14ae5a76a09237e7e2ed4 which make it really difficult to debug

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

BryanMay531 — Thu, 29 Feb 2024 20:53:21 GMT

Agreed, I swear I found a temp gdb somewhere that had the f_.78..... for the field name and the alias was the true field name a few months ago. Can't find it now though

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

RobertKrisher — Thu, 29 Feb 2024 21:39:46 GMT

The temporary gdb is created in a temporary directory, but is cleaned up after running. To see where this is you can run this python code:

import tempfile

tempfile.gettempdir()

Re: Execute Data Load Warning 001156: Could not write value 'NULL' to output field f_7864070e49f14ae5a76a09237e7e2ed4

RobertKrisher — Thu, 29 Feb 2024 21:50:56 GMT

@BryanMay531 I just noticed that you're running the 3.1 version of the data loading tools using a 3.2 version of ArcGIS Pro. The data loading tools were incorporated into the core geoprocessing framework of ArcGIS Pro in 3.2, so I'd recommend you try this again using the Data Management > Data Loading toolbox. Even if it doesn't succeed, you should see some more informative error messages.