Using Dropped Pin when not in field to collect data in child feature loses connection with parent feature

[ChristineTombleson1]

Hi - My field maps app has a parent polygon feature that represents a monitoring site. There are several child features and child inspection tables related to that parent monitoring site. The parent monitoring site must be selected to be able to create a child feature or input data into a related child inspection table realted to that monitoring site.  Protected Shoreline Length (line feature) is a child feature of the parent monitoring site. When a user attempts to create this child feature not in the field (in the office),  the bullseye wants to move to where you are sitting at your desk rather than move to where you want to create the feature at some other location. To solve this, you can press on the screen where you want to drop your point for the child feature, a dropped pin is created at your desired location, and then you select "collect here" which allows you to create your line feature in the location you desire.  However, when the dropped pin is created, the connection to the parent monitoring site polygon is lost.  You can see the polygon goes unselected when the dropped pin is created.  This is a problem since the protected shoreline length will now not be related to the parent monitoring site if created in this way.  Is there a way to fix this issue to allow users to create some features in the office rather than in the field to save time before a site inspection?  Thank you!

[Eugene_Adkins]

In the Field Maps app there is a "collection setting" options (navigate to through the user profile from the maps menu). In "collection setting" there is an option for "related types" that, when enabled, enforces the relationship between features. Perhaps this will resolve your issue?

If the above does not resolve the issue, after you press the collection button you can always move the "bullseye" that appears to the desired location. This may not be the "ideal" solution, but if you know where to zoom to in order to use the "collect here" option then you still know where to navigate to after initiating the collection process to zooms to your location.

Hope one or the other helps.

[imanebenromdhane]

Hi, 

It appears that the main issue lies in the loss of connection between the child feature (Protected Shoreline Length) and the parent polygon (monitoring site) when creating the child feature from the office. To address this issue, you may consider the following steps:

Maintain Connection during Creation from the Office: It may be necessary to update the application to ensure that the connection between the child feature and the parent polygon is maintained even when creating the feature from the office. This might require a modification to the creation workflow.

Geolocation Settings: Ensure that the geolocation settings of the application are correct. The application might be using the office location as the default, and it may be necessary to allow the application to consider the specified location when creating the feature.

Application Update: Check for updates to the application that may include fixes for this specific issue. Updates often resolve operational issues.

Contact Technical Support: If the problem persists, it would be wise to contact the technical support of the mapping application. They may be able to provide assistance tailored to your configuration and the version of the application you are using.

Application Documentation and Forums: Refer to the application documentation and online forums. Other users may have encountered similar issues and shared potential solutions.

In summary, a combination of updates, adjustments to application settings, and possibly assistance from technical support could resolve the issue.