Thanks Doug,
I suspected that index-repeat wasn't refined enough to understand that even if the field was the same, you were going to copy values from another record.
We are also pondering your suggestions with javascript and Field Map and will let you know if we use them.
We may have come up with a more low-level and much "dirtier" solution that has advantages and a big disadvantage.
Instead of making a model like:
Geopoint
Repeat
-date
-note
end repeat
We were thinking of doing a model like this:
-Geopoint
-lastDate
-lastNote
Repeat
-date (hidden, calculate from lastDate)
-note (hidden, calculate from lastNote)
-image* (required)
end repeat
(actually we have many more fields to fill in, mine was just an example to simplify the problem).
Basically, the table structure of the Repeat is almost reproduced on the geographical table which is the one that is compiled on 123.
The fields in the Repeat are automatically calculated by 123 from those in the geographic table.
Therefore, the geographic table becomes a sort of "copy" of the last survey made, and with the Repeat the historicity of the surveys is maintained.
Advantages:
-fields are pre-filled with the last set value
-filters and queries can be made directly on the geographical table within the ArcGIS Online/Enterprise WebApps.
Disadvantage:
-management of value changes on the Web App becomes more difficult: for example, if you need to change a field value from the Web App, you have to do it twice: once for the geographic table and once for the related Repeat table. That is unless you find an automatic mechanism on the Web App.
Was this one of your possible 10 solutions?
Paolo