Hey @JohnathanHasthorpe and @Mandy_Li ,
So it would be passing certain attributes from a certain feature layer (in collector) to a different feature layer (in QC), so not populating the same data set.
If the option to have multiple project user inputs was implemented, that would be a good solution for this, since the custom URL is already being used to launch QC and populate the project user input field.
The primary purpose for us, is to ensure that the feature layer we are using in QC (which is a point layer for collecting initial site evaluation information and photos across the state), has some of the same information as the parcel layers the end-user sees in Collector, and the point layer (from QC) be filtered later. Since this is a statewide dataset, being able to filter multiple levels is key.
Let me know if you have additional questions/comments and i will be happy to provide additional information. Thanks!