I am attempting to send survey data to an existing feature service. The service is set up so that there is one feature layer called MonitoringSites with four related tables. None of the related tables have or need geometries.
I only want to send data into the related tables with the survey, and I want them to be related to existing monitoring sites. Not only that, but in some of the related table repeats, I want to submit multiple records for existing monitoring sites during the same site visit. For example, in one visit, surveyors only need to fill one related entry for SiteConditions, but they will need to take multiple MosquitoSamples.
Using a survey built from the attached spreadsheet in Connect, I can successfully add related records, but when I look at the results in our enterprise database, the data are related to a ghost MonitoringSite. I think the survey as it currently stands just creates a new null geometry with every submission and automatically relates the repeats to that ghost geometry.
Is there a way to prevent this from happening while still maintaining a single survey?
----------------
EDIT#1
Here's the structure of my service/related tables, and my requirements for collection.
MonitoringSites
|_ SiteConditions (1:M, one per site visit)
|_ MosquitoSamples (1:M, ten per site visit)
|_ DiversitySamples (1:M, undetermined per site visit)
|_ WaterQuality (1:M, one per site visit)
EDIT#2
My original idea did not work, I don't think it's possible to only send related data. I ended up making the SiteConditions table a feature class with all the other tables related to that one rather than the MonitoringSites. It's a workaround that got me where I needed to be.