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; } } }

[bug] Batch feature class to feature class

TaylorCarnell1

When running feature class to feature class as a batch tool in ArcGIS Pro and providing multiple input classes or layers, the field mapping shows incorrect schema. Running the tool also produces outputs with incorrect schema.

Can someone please confirm if they can reproduce this or if it is just me.

Thanks

Vind meer berichten getagd met

Accepted answers

All comments

ErinDoody

Hi,

I ran into this issue as well, but in my workflow I found that running a batch project tool gave me all feature class outputs with the correct fields, and not the combined fields of all layers in each layer that batch feature class to feature class was producing.

Dirk

I also have this issue when running FeatureclassToFeatureClass as a batch on 16 input layers (mixture of geodatabase feature classes and shapefiles). It gives all fields of all input datasets to all output datasets. I wasn't sure whether this was by design or not. After reading this thread I tried Export Features, as the bug report suggests the bug is fixed in that tool. Didn't work for me.

I don't want to do anything fancy with field maps. Just want the fields of each input dataset reproduced on each output dataset.

I then tried Export Features on just a single feature class and even that did not faithfully reproduce all field (it dropped a text field for some reason).

The workaround I used was looping the tool in Python rather than running the tool as a batch. Maybe this will help someone else:

The below assumes all input datasets are in their own map and it is currently open in ArcGIS Pro.

# Get current project, map and store map's layers as list
aprx = arcpy.mp.ArcGISProject("CURRENT")
m = aprx.ActiveMap
l = m.listLayers()

# Loop through every layer, sending each to FeatureClassToFeatureClass
for ls in l:
    layerName = ls.name
# Using lyr names as output feature class name, so replacing spaces
    newName = layerName.replace(' ','_')
    arcpy.conversion.FeatureClassToFeatureClass(ls,"<path to output gdb.gdb>",newName)

JoyDRoberts

Link leads to a page with a 404 page not found error. Would love to see the current bug status. Thank you in advance.

JoyDRoberts

Bug is still present in 2.9.5. And if you upgrade to 3.0.2 it really breaks things when you copy and paste FC into new GDB. If there is a domain applied to fields in the FC, even though they are checked to allow null values, it adds a copy of the FC with D_[field name] to your FCs. Really fun. (Yes, I'm going to go research that bug next.)

Sabina

I can confirm the problem using Arcgis Pro 2.8 or 2.9. The bug is on bach tool or using the tool in the model with the iterators on the feature class.

Sabina

Same problem in 2.8.0 on enterprise Geodatabase

TaylorCarnell1

No, iterating FCs in model builder is the only alternative approach I've had as well. You should be able to use the wildcard feature to limit classes it operates on, but yes it will check all candidates in a workspace.
If you're having problems with the field map, I recommend connecting an example class to the FC to FC tool in MB, setting your field map to your liking, the n connecting the iterator back to the tool. It will maintain the field map and apply it to the inputs from each iteration.

TaylorCarnell1

Same problem in 2.8
Came across this thread looking to see if the bug had reported, only to discover it was me 😀

MavTucker

I can confirm this is still happening on local files in Pro 2.7.0

EvanOlivier

I can confirm the same behavior with the Batch FC to FC tool on local file Geodatabase layers in Pro 2.5.2.

EvanOlivier

I am seeing the same behavior with the Batch FC to FC tool on local file Geodatabase layers.

Really a bummer, totally makes this tool useless. Why would anyone use a batch FC to FC tool that destroys the schema of every table except the first in your list of input layers? Crazy stuff. Any movement on your side toward a work around Taylor? I've built an iterative feature class version of this but it takes forever and runs through all layers in a dataset instead of just the selected layers from the user.

I am in model builder trying to fix this but the Field Map parameter is just impossible to get rid of.

@DanPatterson_Retired any updates on this? What is the product plan for it?

Thanks,

Evan

TaylorCarnell1

Thanks Dan, looks to be the same bug, but it appears to apply to layers from independent feature services or even local GDBs as well. Good to know it has been noted, but disconcerting that it was reported August last year.

DanPatterson_Retired

modelbuilder and feature service bug

BUG-000124621: In ArcGIS Pro, using Feature Class To Feature Class ..

nothing specific to your situation I think

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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