Skip to main content
  • EN

I am using the DateTimeConverter in a workbench to convert date and time from an Oracle database to an ArcGIS Online feature service. The autodetect feature works in the workbench and the translation is successful. However, when I upload the workbench to the server, the DateTimeConverter is unable to autodetect the date/time value from the input and the translation fails. Has anyone faced and resolved this situation?

There are many situations where autodetect fails.

Just enter the input format is advised.

Hi @surbhi, I think datetime values read from an Oracle database table can be treated fine with the auto-detect mode usually, but exceptionally, if the datetime field stored <null>, the DateTimeConverter would reject it and cause translation failure. Firstly check if there could be null datetime.

Hi @surbhi, I think datetime values read from an Oracle database table can be treated fine with the auto-detect mode usually, but exceptionally, if the datetime field stored <null>, the DateTimeConverter would reject it and cause translation failure. Firstly check if there could be null datetime.

Thanks, that worked!

 

 

Reply


Community Stats

30,102
Posts
114,271
Replies
37,736
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.