I'm in the process of creating some new surveys in Survey 123 and I wanted to get a better understanding of how repeat tables are related to the survey feature service. If needed, I can create the feature service, repeat tables and relationship classes in Pro for use in Survey 123 but that might not be necessary depending on Survey 123s defaults. By default do Survey 123 created repeat tables have simple or composite relationships class connections to their parent feature services? Is there anyway to change that relationship class of those Survey 123 sourced items from simple to composite or vice versa in Portal or AGOL once a survey is published? If so, will existing record update accordingly? For example, if the default is simple and it's changed to composite, would the change remove any related table records whose parent feature service record was deleted before the change? Thanks!
... View more