When collecting data with a one to many relationship between two point feature classes, it would be helpful to have the child automatically copy the parent's geometry data.
Our city uses an AGO hosted feature service with point feature layer for trees, and a child point feature layer to record tree activity. The activity record should always be at the same location as the tree itself, and users are prone to making mistakes when adding a point manually.
In the past, we've simply used a related table for the tree activity data, without geometry, but we've run into issues trying to visualize the activity data on the map. Creating a join view in AGO resolves this problem, but then we cannot make any modifications to the feature layer's schema while this join is active.
