I am fairly new to Collector and have what I assume is an issue others have long-ago addressed. If this question has been asked elsewhere, I apologize. I found nothing in my brief search.
I have developed a Collector app with a related table for asset management. Each time an inspector goes to an asset, they add a new related record to the table. Easy enough. However, we need to ensure that the individual is really at the asset. As it is now, an individual can be anywhere, select an existing point, and add a related record.
Is there a way to constrain this so that an individual has to be within, say, X distance of an asset to add a related record? Conversely, auto-populating X,Y fields would also serve as a "check." However, based on threads I have seen, this is tricky enough with a feature layer, let alone a related table.
Any insight (even pointing to a different thread I accidentally overlooked) would be greatly appreciated.