Skip to main content

I recently update my file geodatabase schema on a single field that appeared in four feature classes by changing the field types from Text to Integer. My workbench's Esri Geodatabase (File Geodb API) readers and writers are still showing the original Text field type even after deleting them and re-adding. I even rebooted to see if that would help clear it up. Nothing seems to get the readers/writers to update. I had renamed the readers/writers with more suitable names and I noticed that after re-adding them that Navigator had applied the same renamed values, as if it remembered that preference. That makes me think it's storing the connections in cache and it can't update the User Attributes unless that is cleared.

Any suggestions?

Have you tried the Readers\\Update Features Type menu option.

If nothing else works, you can manually edit the reader feature types after setting the option (in Tools\\FME options) "Allow reader feature type editing".


An interesting work-around, but even after updating the readers/writers with the correct field type the processed data did not receive the values, they are all <Null>. The workbench does everything else correctly.

I still think it is stubbornly reading the last schema somehow and it won't accept the new one.


An interesting work-around, but even after updating the readers/writers with the correct field type the processed data did not receive the values, they are all <Null>. The workbench does everything else correctly.

I still think it is stubbornly reading the last schema somehow and it won't accept the new one.

Domains on the field are part of the issue. Removing the domain allowed values to be written, although the readers still show the field to be text rather than integer. I noticed that two other fields with domains were not receiving updates which is how I found part of the problem.

 

 

So to clarify, the readers still show the text type instead of integer which is a real bug.

 

 


Reply