topic Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass in ArcGIS Utility Network Questions

Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MichaelParma — Sat, 28 Jun 2025 13:30:39 GMT

Greetings,

I'm trying to run a batch trace via script in an attempt to speed up processing time on nearly 50,000 records outside of a map, writing summary statistics back to a text field. This is in a FGDB UN with attribute rules disabled. The trace configuration works fine individually and when executed from the Batch Trace dialogue. It fails when this is run from a Python Notebook.

My code:

arcpy.ImportToolbox(r"C:\Path\To\My\UtilityDataManagementSupport_33.atbx", "udms")
arcpy.udms.BatchTrace(
in_utility_network=r"C:\Path\To\My.gdb\Water\UtilityNetwork",
trace_locations=r"C:\Path\To\My.gdb\Water\WaterLine",
result_types="CALCULATE",
trace_config="Trace Config:: Isolating Features",
expression="ASSETGROUP = 1 and AssetType IN (0, 1, 2) and OBJECTID < 6", #OBJECTID is only for testing purposes
output_folder=None,
key_field="GLOBALID",
summary_store_field="analyticnotes",
fields=None,
calc_on_start="UPDATE_START_ROWS",
history_field=None,
default_terminal_id=None,
code_block=""
)

Executing this results in:

ExecuteError: 'in_table' is not a table or a featureclass

In the traceback, I find this line which leads me to believe it might be related to the summary_store_field, though this field exists in the WaterLine feature class.

File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx\udms\logic\un_trace.py", line 1291, in update_starting_points_with_summaries
    logger.exception(e, stack_info=True)

Any thoughts are appreciated!

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

JoshuaBixby — Sat, 28 Jun 2025 14:59:53 GMT

How about posting the entire trackback?

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

PierreloupDucroix — Sun, 29 Jun 2025 21:19:28 GMT

I think the trace_locations parameter in the batchTrace tool should reference a feature layer compatible with the starting_points parameter from the arcpy trace tool, ie. a starting_point feature class : https://pro.arcgis.com/en/pro-app/3.3/help/data/utility-network/starting-points.htm

Did you try building your starting points with the BuildStartingPoints tool from the UDMS toolbox ?

https://esri.github.io/Utility-Data-Management-Support-Tools/docs/3.1/BuildStartingPoints.html

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MichaelParma — Mon, 30 Jun 2025 13:17:31 GMT

The entire traceback:

ExecuteError: 'in_table' is not a table or a featureclass
Traceback (most recent call last):
File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx\udms\logic\un_trace.py", line 1284, in update_starting_points_with_summaries
with arcpy.da.UpdateCursor(
^^^^^^^^^^^^^^^^^^^^^^
RuntimeError: 'in_table' is not a table or a featureclass
Stack (most recent call last):
File "<string>", line 2, in <module>
File "[3]", line 3, in <module>
File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx", line 1287, in BatchTrace
×Ù ä¬¡„ žÅQk Uþr.®E“ƒäA\²ç 6ud¬n ƒ
Í›1Hû @Ò¬M
File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 512, in <lambda>
return lambda *args: val(*gp_fixargs(args, True))
File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx\BatchTrace.tool\tool.script.execute.py", line 23, in <module>
File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx\udms\esri.py", line 547, in wrapper
f = func(*args, **kwargs)
File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx\udms\logic\__init__.py", line 232, in batch_trace
return ts.main(
File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx\udms\logic\un_trace.py", line 835, in main
self.update_starting_points_with_summaries(sum_df)
File "C:\Path\To\My\UtilityDataManagementSupport_33.atbx\udms\logic\un_trace.py", line 1291, in update_starting_points_with_summaries
logger.exception(e, stack_info=True)
Failed to execute (BatchTrace).

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MichaelParma — Mon, 30 Jun 2025 13:19:15 GMT

I have not tried the BuildStartingPoints tool. I was trying to convert the Python directly provided from the the BatchTrace dialogue and figured it might be making that conversion for me.

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

gis_KIWI4 — Mon, 30 Jun 2025 21:27:43 GMT

@MichaelParma - While the error doesn't suggest directly that this is the issue, I think @PierreloupDucroix might be onto something.
The starting point table has a unique schema.

Your script suggests you are pointing to the feature class directly.
If you're passing in a regular feature class (e.g., WaterLine) directly, it may not have the required schema for trace locations.

Instead, you often need to use a prepared Trace Locations table, which is generated using the Add Trace Locations tool.

Maybe that fixes it.

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MichaelParma — Tue, 01 Jul 2025 15:29:29 GMT

Ok, that's does make sense. I think I'll carve out some time to give that a try this afternoon and report back.

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

RobertKrisher — Tue, 01 Jul 2025 16:15:42 GMT

You can find a video of the end-to-end process for configuring batch trace in the GitHub repo for the tool: esri.github.io/Utility-Data-Management-Support-Tools/help/BatchTrace.mp4

You can see that the tool requires you to select a starting point layer created by the Build Starting Points tool.

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MichaelParma — Tue, 01 Jul 2025 17:15:20 GMT

Thanks, Robert. I was unaware of that video. Looks like that's next on my to do list.

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

JohnGoat — Thu, 02 Apr 2026 10:29:24 GMT

Hi @MichaelParma

I am experiencing a similar issue. When working with the data in a Mobile Geodatabase, I can run the Batch Trace Calculate using the same trace configurations without any errors.

However, when I try to run the same data model through a web service backed by Oracle 19c, I encounter this error.

Have you gained any experience with this issue?

PS:

The data schema is the same as in the mobile geodatabase, and no parameters or settings have been changed.

Trace Parameter

arcpy.ImportToolbox(r"D:\...\UtilityDataManagementSupport_3_5).atbx") arcpy.udms.BatchTrace( in_utility_network="L8Network_Utility_Network Utility Network", trace_locations=r"D:\...\Test.gdb\UN_Temp_Starting_Points", result_types="CALCULATE", trace_config="Trace Config:: Adresses", expression="", output_folder=None, key_field=None, summary_store_field="", fields="Test 'Electric Device' UNTest", calc_on_start="SKIP_START_ROWS", history_field=None, default_terminal_id=6, code_block="" )

Error

ArcGIS Pro 3.6.1.59527 udms 3.5 Executing from ArcGIS Pro, 1 map(s), activeMap = True Traceback (most recent call last): File "D:\...\UtilityDataManagementSupport_3_5).atbx\BatchTrace.tool\tool.script.execute.py", line 23, in <module> File "D:\...\UtilityDataManagementSupport_3_5).atbx\udms\esri.py", line 557, in wrapper f = func(*args, **kwargs) File "D:\...\UtilityDataManagementSupport_3_5).atbx\udms\logic\__init__.py", line 232, in batch_trace return ts.main( ~~~~~~~^ where_clause=expression, ^^^^^^^^^^^^^^^^^^^^^^^^ ...<3 lines>... history_field=history_field, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "D:\...\UtilityDataManagementSupport_3_5).atbx\udms\logic\un_trace.py", line 727, in main layer = self.un.create_table(source_id=source_id) File "D:\...\UtilityDataManagementSupport_3_5).atbx\udms\un_helper.py", line 954, in create_table result = arcpy.MakeTableView_management(in_table=path, out_view=out_layer, where_clause=where_clause)[0] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 16735, in MakeTableView raise e File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 16731, in MakeTableView gp.MakeTableView_management(*gp_fixargs((in_table, out_view, where_clause, workspace, field_info), True)) ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 533, in <lambda> return lambda *args: val(*gp_fixargs(args, True)) ~~~^^^^^^^^^^^^^^^^^^^^^^^^^ arcgisscripting.ExecuteError: ERROR 000358: Invalid expression Failed to execute (MakeTableView). Failed script Batch Trace... Failed to execute (BatchTrace).

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

RobertKrisher — Thu, 02 Apr 2026 14:03:13 GMT

@MikeMillerGIS

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

JohnGoat — Mon, 06 Apr 2026 06:26:10 GMT

Yes @MikeMillerGIS pls help me 🙂

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MikeMillerGIS — Tue, 07 Apr 2026 13:00:55 GMT

Are you running this in Pro or outside of pro? You are listing the describe name of the UN Layer "

 in_utility_network="L8Network_Utility_Network Utility Network",

Can you change that to the full url path?

How did you get that name in the tool?

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

JohnGoat — Thu, 09 Apr 2026 10:45:08 GMT

Yes, I am running this tool from within ArcGIS Pro. If the Utility Network layer is present in the active map, it appears in the dropdown with its name.

When I try using the full URL path as suggested, I still get the same error.

@MikeMillerGIS

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MikeMillerGIS — Thu, 09 Apr 2026 11:24:05 GMT

If you run the same Batch Trace via the GP tool and not the notebook, same error? I have a lot of debug statements around this code area. Can you turn on debug logging and run it through GP(not a notebook) and share the results?

To enable debug logging

- First open the toolbox and open any tool. Fill it out and run it. You can immediately cancel it. This loads the embedded python module in memory

- Open the Python window in ArcGIS Pro(not a notebook)

- Enter the following

import udms
udms.logger.setLevel('DEBUG')

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

JohnGoat — Thu, 09 Apr 2026 14:07:14 GMT

Yes, I get the same error when running it with notebooks and the GP tool as well.

@MikeMillerGIS

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MikeMillerGIS — Thu, 09 Apr 2026 14:10:33 GMT

That is only the first 52 lines, can I get all the messages?

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

JohnGoat — Thu, 09 Apr 2026 14:20:57 GMT

I didn't add it because the error message is the same; all the error messages are like this, Mike.

Start Time: Thursday ArcGIS Pro 3.6.1.59527 udms 3.5 Executing from ArcGIS Pro, 1 map(s), activeMap = True ****PARAMETERS**** Input Utility Network: https://unw-server.com/server/rest/services/EA_Test/FeatureServer/8 Trace Locations: Electric Device Result Types: ['CALCULATE'] Trace Configuration Name or Field: Trace Config:: Adresses Expression: None Output Folder: None Group Field: None Store Summary Information on Starting Points: None Fields to update: [['Test', 'Electric Device', 'UNTest', 'FIRST']] Calculate on Starting Point Features: False JSON Result file folder: None Aggregated GDB: None Historical Date Field: None Stat Table: None Default Terminal ID: 6 Code Block: None ****ENVIRONMENTS**** udms.logic.batch_trace( utility_network=<arcpy._mp.Layer object at 0x0000021628AC77A0>, trace_locations=<arcpy._mp.Layer object at 0x0000021628B07750>, result_types=['CALCULATE'], output_folder=None, summary_store_field=None, field_mapping=[['Test', 'Electric Device', 'UNTest', 'FIRST']], key_field=None, expression=None, trace_config='Trace Config:: Adresses', calc_on_start=False, history_field=None, default_terminal_id=6, user_code=None, ) In Path: https://unw-server.com/server/rest/services/EA_Test/FeatureServer/8 URL: https://unw-server.com/server/rest/services/EA_Test/FeatureServer workspace: https://unw-server.com/server/rest/services/EA_Test/FeatureServer Path: https://unw-server.com/server/rest/services/EA_Test/FeatureServer UN Loaded Collecting Trace Configs Validating the inputs Trace Config:: Adresses Setting up parameters Opening Data Element Verifying calc fields Verifying Lookup Fields and Target Tables Source ID: 9 udms.logic.batch_trace 73.46496698597912 Traceback (most recent call last): File "D:\...\UtilityDataManagementSupport_3_5.atbx\BatchTrace.tool\tool.script.execute.py", line 23, in <module> File "D:\...\UtilityDataManagementSupport_3_5.atbx\udms\esri.py", line 557, in wrapper f = func(*args, **kwargs) File "D:\...\UtilityDataManagementSupport_3_5.atbx\udms\logic\__init__.py", line 232, in batch_trace return ts.main( ~~~~~~~^ where_clause=expression, ^^^^^^^^^^^^^^^^^^^^^^^^ ...<3 lines>... history_field=history_field, ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ) ^ File "D:\...\UtilityDataManagementSupport_3_5.atbx\udms\logic\un_trace.py", line 727, in main layer = self.un.create_table(source_id=source_id) File "D:\...\UtilityDataManagementSupport_3_5.atbx\udms\un_helper.py", line 954, in create_table result = arcpy.MakeTableView_management(in_table=path, out_view=out_layer, where_clause=where_clause)[0] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 16735, in MakeTableView raise e File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\management.py", line 16731, in MakeTableView gp.MakeTableView_management(*gp_fixargs((in_table, out_view, where_clause, workspace, field_info), True)) ~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\geoprocessing\_base.py", line 533, in <lambda> return lambda *args: val(*gp_fixargs(args, True)) ~~~^^^^^^^^^^^^^^^^^^^^^^^^^ arcgisscripting.ExecuteError: ERROR 000358: Invalid expression Failed to execute (MakeTableView). Failed script Batch Trace... Failed to execute (BatchTrace). Failed at Thursday, April 9, 2026 5:00:10 PM (Elapsed Time: 1 minutes 30 seconds)

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MikeMillerGIS — Thu, 09 Apr 2026 14:30:06 GMT

Can you try with 3.5.1 version of the tools. I am expecting to see more info in the debug log. There should be a message above the error with info that can help track down what is going on. Your issue is different than the original post. This is failing to create a table view on the UN class.

https://github.com/Esri/Utility-Data-Management-Support-Tools/releases/download/3_30_2026_3_5_1/UtilityDataManagementSupport.atbx

Re: Batch Trace Script: ExecuteError: 'in-table' is not table or a featureclass

MikeMillerGIS — Thu, 09 Apr 2026 14:32:37 GMT

actually hold off, let me add a few more debug statements, the lower level function does not have any