Ok, so you're looking for specific documents. Meaning: The filename (or some attribute) has to match certain criteria before that switch is flipped. AND, you're going to have multiple Yes/No's (at least two, so far, right?). Is this correct so far?
Things to consider, if this is true:
- filename (or other criteria attribute) must be exact on the upload.
- What happens if we upload a random file? (Nothing, I presume)
- What happens when the file is uploaded more than once?
- What happens when someone decides we now need a third document? (how to make the solution scalable).
If the document upload is part of a process or a journey, you might want to consider a Business Process Flow. You can build these in Power Automate, but they are also native in D365. This is the thing that lets you map out a process at the top of the form with certain phases and milestones.
The way Out-of-the-box D365 connects to SharePoint, it wants to create a subfolder for each record in that entity. So, if you're looking at Accounts, there will be a folder for each different account. Combine this with how the SP trigger works in a flow, and it wants to watch a specific folder for a new upload. This means you'll have a hard time when new accounts are added, and you might have to build a flow for each account. (this is why I'm still on Team Workflow for this thing).
If the document upload is part of a process, it might be a good idea to look at the entire process and build a digital solution to match that. Either way, keep us posted.
-Ed-
If you liked this reply, please give it a thumbs up! If this reply has answered your question or resolved your challenge, please consider marking it as a Solution. This helps other users find it more easily via search.
