@JimJim I have done something similar in past so I will try to answer your queries:
1. I wanted to ask about storage, there are a possible 9 different approvers for each request, I need to capture the decision of each approver including the date and any comments. Should I store these details in a separate table? Coming from a SQL background it doesn't make any sense to store everything in the one place.
Makes more sense to store all relevant information for a request at one place as if you keep in different places, you will have to make calls for everything which will add more actions and api calls unnecessarily, with just one action if you get the record all relevant information would be available.
2. Should I be using Sharepoint List or CDS? I assumed Sharepoint List but that's only because I hadn't heard of CDS until today. My company has premium license for Office 365
Yes SharePoint is a good option as its just going to be a simple app for approvals and I have not worked with CDS but I think there would still be some charge, so SharePoint is easy to manage and free so SharePoint it is.
3. Design considerations for the flow itself, I was thinking of a modular approach, having a flow for the approver work, being called and controlled by a master flow. Does this seem like a reasonable approach?
You can try parent child flow and yes having different flows for different stages of request will help you keep the flow easy and light also in case of issues it would be easy to find and pin point issues
Hope this helps.
--------------------------------------------------------------------------------
If this post helps answer your question, please click on “Accept as Solution” to help other members find it more quickly. If you thought this post was helpful, please give it a Thumbs Up.
