This is very conveniently solved in Survey123. Waiting for implementing something similar to Collector too!
I agree that this would be a great addition to the collector apps functionality. Our users are currently scrolling through multiple fields to collect the correct data. With a smart form solution this could be solved by assigning specific fields to show through the selection of another field.
Smarter data collection forms are on the 'Planned' feature improvements coming to Collector app in the future. See the Sneak Peek section, Sneak peek—Collector for ArcGIS | ArcGIS.
Denise King | Technology Lead - Apps/Mobile
Esri Support Services
To implement lookups in collector we need to create database domains. This can be better done through the software using xml definition schemas. Another method is to use xls as in forms.
No need to waste considerable time on the data structure unless its used that way at source and most of the time it isnt, its just for collection. Using a sledgehammer to crack a nut
Working for a Florida Water Management District, we use this app to capture, review, repair, and report on various problems encountered when inspecting our flood control system. Collector is perfect, except for the lack of branched logic. We are currently using a weird hybrid of both Collector and Survey123 (pointed to the same database), which is not ideal. We are VERY EXCITED about the idea of branched logic being implemented in or supported by Collector.
As I've said many times before, we need Collector123. Forms are great in Survey123, but the maps suck. Maps are great in Collector, but data collection is clunky compared to the smart forms in Survey123.
Why not create a form framework that applies across the entire ArcGIS Solution? These one off applications authored by different development teams which do something the other applications should/could do is just as frustrating.
For example why can't the same feature layer be added to Web App Builder Editor Widget with the same "smart form". If all applications can access the same data service, should data integrity be applied consistently across the platform?
Some things to consider. Attribute Rules and Contingent Values (currently implemented via ArcGIS Pro and shared, if need be via hosted web layer in ArcGIS Enterprise)... These seem to be two new "data design" areas that esri is making investments. These things occur at the data level so theoretically this is app agnostic (should work in Collector). I'm currently trying to test these via a 10.7 ArcGIS Enterprise implementation but am running into issues with offline/sync enabling Attribute rules. In any event, this looks very promising and the tests I've run so far look like game changers. Things like "if I enter this value 'x', make the value there 'y'" or "when I create a new feature populate the InpsectionDate field with today's date" or "this is a sequential field... when I add a new feature calc the value of this field to the last number in the sequence + 1". All this done via Arcade expressions. Contingent Values is more of the smart pick-list thing. If I choose 'x" in this list, then only show values of x,y,z in this other list.
This stuff has been A LONG TIME coming and I can't wait to start redesigning our processes and systems to take advantage of these features.
Retrieving data ...