 Azure says, I have a flow with multiple layer approvals triggered by when a new response is submitted. The form has 80 questions. What is the best option for the approver to view the response answers from the form? It's quite messy if I drag all the dynamic contents from the form into the email content. Is it possible to the approver to view the form response in the same as a respondent copy? So many good answers for this. No. The fact that the form has what? 80 questions like we're talking serious, and it's probably going to have to be a custom or bespoke type solution that will allow you to do it. But that sounds bigger than it is, right? It could be as simple as putting that midstream responses out to a central location for viewing. What are you thinking, Sharon? That's exactly what I was being sarcastic. I got 80 questions. So I actually had to deal with this. This last summer we did a conference, I helped somebody with a conference, and they basically did the same thing. They had all these busy questions. I want to say they had 75 questions in the form. So ultimately what we ended up doing was we ended up building a Power Automate workflow that basically grabbed the information out of the form and put it into a spreadsheet. I mean, nine times out of 10, that's the best way you're going to have. You could put it in a SharePoint list if you really wanted to be a really wide SharePoint list with a lot of views, but spreadsheets, I mean, good old handy spreadsheets. I think by default, the form's data, the responses will end up in a spreadsheet. The thing that you'll have to ask yourself is, is it okay for others to see those entries? So it is a complicated thing. You have the tools and there's the options within the toolset to customize the solution, but it's a solution build. I think in the approvals app inside of Microsoft Teams, you get to see the status of where it is and that multi-approval flow, but this is a separate thing because you're totally bespoke with what you're describing. I mean, if you did it, I guess one of the options is, I was going to say outside of a custom solution, because the custom solution is you could basically build a view for them to look at that would take that information and basically flip it around for them to look through it, but yeah. With InfoPath, right? Yeah. Yeah, InfoPath. It depends what you want to do. Yeah. It depends. Yeah. I mean, if you're, I was thinking about this of, yeah, this is another classic question where follow-up questions would be fantastic for Azure to figure out what they really want to go and do. My first thought was that for each response being able to look at all the answers to that, the other person, if I'm driving, there's multiple people driving to the forum, there's some trigger that because back to me is the person that originated that request to that person just so I can verify the results of that. Then I want to see or I want to see an aggregate of all the people that I've driven, or do I want to see all the people that I've driven to the forum across all answers to the forum that, so there's three different ways of looking at that data right there, but yeah, there's depending on what they're trying to do. Power BI solution could be really good too. If you grab the information, dump it into a data source like Dataverse or something and then pull it back into a Power BI report, then they would have, I mean, it would obviously, this is like a solution as it comes, right Norm? But then they could have kind of an interactive drill down viewable option to see it in a very pretty way. Indeed. My first reaction is like 80 questions is a lot, especially if it's multi-layered approvals, and I might be dividing that work into logical chunks. So get to the first approval and we call it phase one, and then if they get through that stage, then they come into phase two and phase three and so on, to make the complexity lower to see the stages and the responses out at those different parts of the end gate, if you will, before it gets into the next phase, and then you can get the analytics. You have something that's a little more supportable. You won't run into that 30-day timeout that we have to unfortunately live with Power Automate on an approval. So after 30 days, it just times out and you lose it. So that's always a danger. If you have something with 80 questions, there's a good chance that that's going to take a long time to run through. More importantly, what are the analytics on abandonment for the form and the workflow like you mentioned? Yeah. 30 days, workflow being intended to replace long-running processes. It seems like 30 days is a really arbitrary, maybe low-end timeline to pick, but I guess in terms of systems and storage, you could end up if you don't set something, it's going to blow out your storage and process tracking. So I don't know. On paper, 30 days sounds great. Just tack in a few long weekends or a vacation or. Some of the companies we work with. Yeah. That'll chew up 30 days pretty quick. Just thinking of all the automated email reminders for each step phase where it pauses after how for how much time that they've not moved it forward to that next step. Your mandatory training is 78 days overdue.