I'm wondering if anyone has used Survey123 for this already or if Survey123 plans to support the following workflow.
I have an enterprise geodatabase with an existing data structure where there's a point feature class containing 'AirQuality_SampleSites'.There's also two tables called 'AirQuality_FieldData_TSP' and 'AirQuality_FieldData_PM25' these two tables contain the data collected from instruments at the sample sites. There is a 1 to Many relationship class relating the 'AirQuality_SampleSites' to the 'AirQuality_FieldData' tables with a field called 'STATION_ID' (with the postfix '_PK' and '_FK' to distinguish between primary and foreign keys).
With this current structure we have been entering the instrument readings into those two tables with a domain on the 'STATION_ID' so the relate works correctly no matter how the records are added. This works perfectly for our web apps and in ArcMap. We've also used collector to add related records but it really isn't an ideal way to enter data like this.
So it would seem that a form-centric approach like Survey123 would be perfect for the purpose of adding records to our related tables. Essentially what i'm envisioning:
I understand that support for adding to existing feature classes in a federated environment with an enterprise geodatabase is coming. But I'm curious if this sort of situation where were simply putting new rows into a table is on the horizon too?
If anyone is in a similar situation I'm curious if you've found a workaround or alternate solution to this.
The workflow of adding records to a table related to a feature class is already supported; the part we don't have support for is working with a federated service. We have a knowledge base article that describes the process of adding an existing stand-alone ArcGIS Server Service; once the service is added, an XLSForm can be generated form the service's definition (which includes all layers). The XLSForm can then be edited and configured to work with the related table only (removing other layer's fields and setting the form_id to the related table (refer to FAQ: How do I author a Survey123 for ArcGIS survey that matches a feature service? ).