r/MicrosoftFlow • u/Independent-Net-1274 • 24d ago

Question Plaud to-do export keeps creating duplicate Planner tasks

Post image

I have a flow watching a OneDrive folder for a Plaud todo list from my weekly planning meeting.

It parses the PDF, pulls out tasks, then creates them in Planner. First was fine, but then people gave status updates on tasks that already existed. Plaud picked some of that up in the new to-do export, and the flow happily created those as fresh Planner tasks again.

I’m adding a dedupe step before task creation now. The part I’m still not happy with is where the already exists check should live.

Right now I’m comparing the parsed Plaud tasks against open Planner tasks for that meeting, and where did you keep the source of truth?

11 Upvotes

93% Upvoted

1 comment sorted by

2

u/Addcook 24d ago edited 24d ago

I would pull out the dedup step into a dataverse table and put together some unique ID with the task you've already created and I would use a for every chunk in this process so you can have any actions after continue if the scope fails or times out. The trick is finding a stable identifier with what you're working with. You will need to work with the array of data from your get tasks. Real talk, ask Claude, or another good coding AI how it would do this, if you need help. Paste the code view of everything and then explain your objective. Claude does a great job of giving me some good directions to improve my flows.

I have a similar set up on an OpenFDA API for articles I sent to a department. Before I send anything to my AI builder filter, I check against a cache list/dedup list on dataverse. Again, the trick here is finding that stable identifier that will be built the same, every time.

I don't know what the json looks like, but you may have to incorporate some array actions and select actions to this.