I did not reorder the IDs initially (Pipes ID = 0 and the table ID = 1), and I could not get s123 to publish the survey. Again, I published a pipes layer and a related table to AGOL, and below is a snip from that Feature Service's URL...
http://services.arcgis.com/0hWR1h1PHFoPztOo/arcgis/rest/services/surl_pipes0/FeatureServer
So, in an effort to populate a submission URL specifically for the related table, I used the following URL (note the "/1" at the end to point directly to the table, and not the pipes):
http://services.arcgis.com/0hWR1h1PHFoPztOo/ArcGIS/rest/services/surl_pipes0/FeatureServer/1
The following is the result when trying to publish my survey:
My next thought was that adding the "/1" is what is fouling things up, so I replaced the above submission URL with the following (simply excluded the "/1"):
http://services.arcgis.com/0hWR1h1PHFoPztOo/ArcGIS/rest/services/surl_pipes0/FeatureServer
As a result, I was able to publish the survey, but when trying to submit a survey, I get the following error:
This led me to believe that by using this URL (http://services.arcgis.com/0hWR1h1PHFoPztOo/ArcGIS/rest/services/surl_pipes0/FeatureServer) and not specifying a layer ID at the end, s123 looks at whatever layer in the feature service has an ID of 0 (in this case, the pipes), hence "incorrect geometry" error.
So, that is why I tried switching the IDs around so the table is 0 and the pipes 1 when publishing the feature service, thinking a submission URL requires no "/#" appended to the end. And like I said before, doing this allowed me to publish the survey and submit data, but when publishing the pipes/table feature service, I lose the features in my pipes on AGOL.
Maybe I am going bout this all wrong - I'm sure there is a way to populate the submission URL to write to a table regardless of its ID, but what am I doing wrong? How can I populate the submission URL with a valid URL that points directly to my related table that has an ID of 1, or any number for that matter?
Thanks for your responses thus far, I'm really hoping I can get this to work as I foresee a large time-savings by submitting survey data to a table that has a relationship already in place with the pipes layer.
Sam