This feels like possibly turning the intended logic around where you create a point for each survey entry. What about long-term infrastructure.
Let's say we have an annual bridge inspection form and then a 3 year inspection form, each have differing questions/requirements. There might possibly be a that stores a URL to the annual survey and another field to the 3 year survey (no fancy calculated expression or anything).
Let's also assume that said bridge doesn't have notoriety like 'Best bridge ever!', but there are in fact hundreds of bridges and a simply a numerical identifier.
Let's then say we have a regional manager who doesn't know anything about S123 but wants to click on a particular bridge in a web app and see all the past forms associated with it. How might we achieve that?
It's possible that we could create some PowerAutomate logic that shunts the outputs of the surveys into a folder, but then there would have to be either a folder for each bridge or some ugly naming convention where the bridge ID is part of the file output name and then the manger has to sort by ID...all less than convenient.
