Hi,
This may be quite a niche one but hoping someone can assist. I'm using survey123 to capture data and I have two versions of my form, one for regular users and one for managers. The manager one has full access to the dataset and the user one utilises a view that doesn't allow editing of other users data.
I have two flows set up so that when either of these forms are used they check for new entries to the underlying dataset or view and then create a task in Microsoft planner. The trigger I'm using is "When a record is created in a feature layer" and then I'm using "Fetch updates, changes, or deletions from feature layer" to get the details to use to create the planner entry. As far as I could tell I needed two flows as the trigger has to be against the layer that is edited (even if it is a view).
The issue I'm having is that my flows are creating duplicate entries in the planner. The issue seems to be that if a user uses one version of the form and creates a new entry that runs fine. But then if another user uses the other version of the form then "Fetch updates, changes, or deletions from feature layer" pulls not just the new entry that triggered the flow but those from when the dataset was updated from the other survey too. So one new entry may have been created in the form but previous entries created when the other form was run are included in the outputs.
Is there any way to prevent this? Ideally I want "Fetch updates, changes, or deletions from feature layer" to only process the changes that triggered the flow. Is there any way to limit this?
Any assistance on this would be much appreciated.
Thanks
Anthony
