This is relativity easy. Add all the old data to a CSV, toss that CSV into the media folder, and use pulldata.
https://community.esri.com/t5/arcgis-survey123-blog/work-with-csv-data-in-arcgis-survey123/ba-p/1157...
and
https://community.esri.com/t5/arcgis-survey123-blog/survey123-tricks-of-the-trade-pulldata-quot-laye...
Regarding data collection, you have a couple choices, both with pros and cons. Assuming there is old data for a tree:
- You can populate your fields with the old data let people. Users can overwrite the old data as needed. This is a simple set-up, but may result in a user forgetting to update a field since it already has old data in it.
- You can add a select_one yes_no to toggle between text fields with pulldata() and readonly=yes (i.e., fields with pre-populated old data that cannot be changed) or blank fields. This is probably the best option for ensuring quality data, but would require more effort to make. If going this route, I would suggest using a third field in conjunction with the first two. The third field would be a calculate with this equation: coalesce(${q1_text},${q1_autopopulated}). This could be used for any output/field notes so you don't have to double up on fields in the Feature Report.
