Survey123 Inbox Order - ArcGIS Server Feature Service - Oracle DB

[Ohan_GeoDecisions]

Case: A Survey123 published using an ArcGIS Server Feature Service reading from an Oracle Database.

In the Survey123 Mobile App, using Inbox has 2 options for Ordering:

• A to Z
• Time based

The ArcGIS Server Feature Service reading from an Oracle Database with Tracking Enabled adds the fields: CREATED_USER, CREATED_DATE, LAST_EDITED_USER, LAST_EDITED_DATE

The Time Based Ordering does not work based on LAST_EDITED_DATE 

Any recommendations? or Future changes or workarounds ? James Tedrick Ismael Chivite‌ 

[JamesTedrick]

Hi Ohan,

Can you confirm that Editor Tracking is enabled and reported at the feature service endpoint?  If so, it sounds like there is a bug when working with your service.  It would be helpful if you could open a support ticket so the issue could be identified.

[Ohan_GeoDecisions]

Hello James,

Yes, i confirm that tracking is enabled, here is the service endpoint settings:

{"currentVersion": 10.41,"id": 0,"name": "blabla","type": "Feature Layer","description": "","copyrightText": "","defaultVisibility": true,"editFieldsInfo": {"creationDateField": "created_date","creatorField": "created_user","editDateField": "last_edited_date","editorField": "last_edited_user"},

and then a few lines down:

{"name": "CREATED_USER","type": "esriFieldTypeString","alias": "CREATED_USER","domain": null,"editable": false,"nullable": true,"length": 255},{"name": "CREATED_DATE","type": "esriFieldTypeDate","alias": "CREATED_DATE","domain": null,"editable": false,"nullable": true,"length": 8},{"name": "LAST_EDITED_USER","type": "esriFieldTypeString","alias": "LAST_EDITED_USER","domain": null,"editable": false,"nullable": true,"length": 255},{"name": "LAST_EDITED_DATE","type": "esriFieldTypeDate","alias": "LAST_EDITED_DATE","domain": null,"editable": false,"nullable": true,"length": 8},

We will create a ticket and follow this up, Thank you for your help