Return to Question

added screenshots of calculate tool

edited Mar 3, 2016 at 16:53

matthewiannowlin

395
3
12

I have the following model:

In my two FC to FC tools shown above, I rename many fields. For example, table 1 has field "MEAN" and I rename it "approval_rate." Table two has "approval_rate" and I rename it "approval_rate_old." I join those two tables with renamed fields, and then run calculations on the fields by their new names (starting with Calculate Field (2)).

However, Calculate Field (2) fails, even though I have the syntax and field names correct in my simple VB expression. I think it is failing because FC to FC (2) is not changing the alias, just the field name. So when I open the resulting attributes table, it still shows all the previous names. In the example above, this leads to two fields with the alias "approval_rate" in the same table. So when Calculate Field (2) goes to run an expression using "approval_rate" it does't know which field to use and thus fails with "General Exception Error."

Does my hypothesis seem correct? Why is one FC to FC tool changing the name and alias, and one is only changing the name, not the alias?

Here is the screenshot of my Calculate Field (2) tool.

And here are screenshots of the relevant columns in the input table.

I have the following model:

In my two FC to FC tools shown above, I rename many fields. For example, table 1 has field "MEAN" and I rename it "approval_rate." Table two has "approval_rate" and I rename it "approval_rate_old." I join those two tables with renamed fields, and then run calculations on the fields by their new names (starting with Calculate Field (2)).

However, Calculate Field (2) fails, even though I have the syntax and field names correct in my simple VB expression. I think it is failing because FC to FC (2) is not changing the alias, just the field name. So when I open the resulting attributes table, it still shows all the previous names. In the example above, this leads to two fields with the alias "approval_rate" in the same table. So when Calculate Field (2) goes to run an expression using "approval_rate" it does't know which field to use and thus fails with "General Exception Error."

Does my hypothesis seem correct? Why is one FC to FC tool changing the name and alias, and one is only changing the name, not the alias?

I have the following model:

In my two FC to FC tools shown above, I rename many fields. For example, table 1 has field "MEAN" and I rename it "approval_rate." Table two has "approval_rate" and I rename it "approval_rate_old." I join those two tables with renamed fields, and then run calculations on the fields by their new names (starting with Calculate Field (2)).

However, Calculate Field (2) fails, even though I have the syntax and field names correct in my simple VB expression. I think it is failing because FC to FC (2) is not changing the alias, just the field name. So when I open the resulting attributes table, it still shows all the previous names. In the example above, this leads to two fields with the alias "approval_rate" in the same table. So when Calculate Field (2) goes to run an expression using "approval_rate" it does't know which field to use and thus fails with "General Exception Error."

Does my hypothesis seem correct? Why is one FC to FC tool changing the name and alias, and one is only changing the name, not the alias?

Here is the screenshot of my Calculate Field (2) tool.

And here are screenshots of the relevant columns in the input table.

asked Mar 2, 2016 at 19:41

matthewiannowlin

395
3
12

Feature Class to Feature Class renames field, but not alias

I have the following model:

In my two FC to FC tools shown above, I rename many fields. For example, table 1 has field "MEAN" and I rename it "approval_rate." Table two has "approval_rate" and I rename it "approval_rate_old." I join those two tables with renamed fields, and then run calculations on the fields by their new names (starting with Calculate Field (2)).

However, Calculate Field (2) fails, even though I have the syntax and field names correct in my simple VB expression. I think it is failing because FC to FC (2) is not changing the alias, just the field name. So when I open the resulting attributes table, it still shows all the previous names. In the example above, this leads to two fields with the alias "approval_rate" in the same table. So when Calculate Field (2) goes to run an expression using "approval_rate" it does't know which field to use and thus fails with "General Exception Error."

Does my hypothesis seem correct? Why is one FC to FC tool changing the name and alias, and one is only changing the name, not the alias?

arcgis-desktop modelbuilder