I seem to be having issues with the features service data types when I am updating a service with new data from a csv or excel. It appears that that some data types as read from the excel are not consistently translated to esri's schema (or are being assigned in some weird way in from the excel input). I get various errors trying different things. I thought I might try to force the incoming data to conform to whatever esri wants it to be. I might avoid all sorts of gotchas from the excel. In the schema file, can I set the data type to the expected esri one. I have tried but it seems to set anything I change to String.
Page 1 / 1
Hi @ianh ,
Have you tried setting the Attribute Definition in the writer feature type to Manual and setting the data types as they appear in AGOL? If so and you are still running into issues, can you please include the log file or section of the log that shows the errors/warnings?
Thanks Chris, taking a step back was helpful. I was trying to coerce the data to types that were more relevant in attribute manager, but was running into type conversion errors. In the end I took your advice. I left untouched anything coming from the excel that seemed to be floating point numbers and set them to esri double, anything else causing me problems I converted to esri string - in the manual settings of the writer. This has solved my problem, thanks.
Thanks Chris, taking a step back was helpful. I was trying to coerce the data to types that were more relevant in attribute manager, but was running into type conversion errors. In the end I took your advice. I left untouched anything coming from the excel that seemed to be floating point numbers and set them to esri double, anything else causing me problems I converted to esri string - in the manual settings of the writer. This has solved my problem, thanks.
Great, thanks for following up to let us know you got it working!