Skip to main content
  • EN

I have a workflow where I am truncating an existing gdb table and a single attribute value is not being constantly output.

 

The target attribute is a text field with a length of 50. The values that are supposed to be output to that field are all less than that length.

 

About half of the time I run the workspace, it correctly outputs the values as expected. The other half of the time many but not all of the values come across as an empty string. It seems to switch back and forth between outputting correctly and encountering the issue.

 

Regardless of if the issue occurs or not, the feature cache at the final transformer of the process always shows the field fully populated as it should be. The issue happens while the data is being truncated to the gdb table.

 

When the output is viewed in ArcGIS Catalog, the field has an asterisk next to it, and is the only field in the dataset that has it. From what I've seen while researching that means this field is indexed, but I'm not sure how that exactly correlates/causes the issue I have described. It is also the only field in the dataset where this issue occurs.

 

Edit: I should also note that the transaction type of the writer is an edit session, and the target gdb table participates in a relationship class with another feature class in the same gdb that also gets truncated in the same process.

 

Does anyone have any insight into how to fix this issue? I have an open support ticket but figured It could help to ask here as well.

 

Thanks in advance.

Whats the field name your trying to write to?

Whats the field name your trying to write to?

UniqueGISID - which is a concatenation of two other attributes also present in the dataset. From viewing the feature caches I have confirmed that the issue does not happen until the data flow hits the writer.

 

Also note that a polygon feature class in the gdb also has the same attribute (but calculated from a different input values) and the issue doesn't ever happen there.

 

The UniqueGISID attribute is what the relationship class between the table and the poly feature class is based on.

UniqueGISID - which is a concatenation of two other attributes also present in the dataset. From viewing the feature caches I have confirmed that the issue does not happen until the data flow hits the writer.

 

Also note that a polygon feature class in the gdb also has the same attribute (but calculated from a different input values) and the issue doesn't ever happen there.

 

The UniqueGISID attribute is what the relationship class between the table and the poly feature class is based on.

Sweet, just wanted to make sure it wasnt a reserved filename in Esri land. What writer are you using? The API GDB Writer or the Licensed GDB writer? Be worth trying with the one you're not using

UniqueGISID - which is a concatenation of two other attributes also present in the dataset. From viewing the feature caches I have confirmed that the issue does not happen until the data flow hits the writer.

 

Also note that a polygon feature class in the gdb also has the same attribute (but calculated from a different input values) and the issue doesn't ever happen there.

 

The UniqueGISID attribute is what the relationship class between the table and the poly feature class is based on.

I'm using the licensed gdb writer. I cannot use the open api gdb writer because the target table is a part of a relationship class, which is not supported by that writer type.

Reply


Community Stats

30,024
Posts
114,013
Replies
37,641
Members
Terms & ConditionsCookie settings