I have a fairly straightforward workspace writing out one AGOL feature class with a large schema (American Community Survey data). After running the writer the translation log shows 26 features successfully written, however, the resulting AGOL feature class only has one feature.
I am stumped as to why this might be happening as I've worked with AGOL writers pretty frequently and never encountered anything like this. Any advice?
+47Check out the warnings In the log file. Could be there are attributes with values which don't match a columns schema (e.g. a string in a number column).
I was authoring the feature class for the first time and trying to set the fields manually but letting the writer run with an automatic attribute definition did the trick. Although, I'm concerned I won't be able to use the data for the exact purpose I'm hoping for if the field type is a string, is there a way around this?
+47I was authoring the feature class for the first time and trying to set the fields manually but letting the writer run with an automatic attribute definition did the trick. Although, I'm concerned I won't be able to use the data for the exact purpose I'm hoping for if the field type is a string, is there a way around this?
Setting the feature class schema manually should also work but you will need to make sure that the attributes going to it match the definition. You can try and use an AttributeValidator before the writer to check the required attributes and types fit the defined schema.
If you want to try to make sure all features are either written or no features are written you can use a FeatureHolder after the Validator to wait for all features to be checked. On the failed port you can either use a logger (followed again by a FeatureHolder and then a Terminator) to get the details of what is invalid or you.
If it's really critical you can also switch out your Writer with a FeatureWriter and then, after all have been written you can read in the written features with a FeatureReader and perform a join on the ID. Any features which don't join you can save to a separate file for fixing.
