Others have written this up, and I smoothed out the errors I was hitting through Matthew's blog post here. However, I wanted to draft up a slightly different take just to clarify some gotchas as well as solidify the use-case.
This approach fits w/ a series of other posts I've done on:
- allowing users to interact w/ SharePoint data they don't have rights to
- reading JSON data into Collections using Power Automate
- writing JSON data from Collections using Power Automate
And even with:
All of these build into an ecosystem of very supportable and deployable applications that create a minimum of fuss while also being highly adaptable and portable across scenarios.
