Power Automate makers: you don't need a loop to filter 400 rows down to 18.
Filter Array. Select. Join. Compose. Parse JSON.
These 5 actions eliminate 80% of the unnecessary loops I see in production flows.
@kailashr2k
- 2 Followers
- 0 Following
- 112 Posts
If you have copy-pasted the same logic into three different Power Automate flows, you have already created a maintenance problem.
Child flows exist for exactly this. Build it once. Call it from anywhere.
http://mytrial365.com/2026/05/07/stop-copying-logic-across-flows-use-child-flows/
Power Automate hot take: "Scope", "Compose", and "Condition" are not action names. They are placeholders you forgot to fill in.
Six naming rules that will make your flows actually maintainable 🧵
http://mytrial365.com/2026/04/30/stop-naming-your-flow-actions-scope-and-apply-to-each/
🔄 Part 6 is live: Migrating from Office365 / WS-Trust to Modern OAuth in Dataverse
Still using AuthType=Office365? It’s time to modernize.
🔐 Why legacy auth breaks
⚙️ Moving to OAuth / ClientSecret
☁️ Supporting MFA & Conditional Access
🛡️ Security best practices
Authentication isn’t just setup it’s architecture.
If you maintain older Dataverse tools, this one’s for you.
🌐 Part 5 is live: Calling Dataverse from a Single Page App (SPA)
No backend.
No proxy.
Just MSAL + OAuth + Dataverse Web API.
In this post I break down:
🔐 Token acquisition with MSAL
🌍 CORS configuration
⚙️ Delegated user security
💻 Real JavaScript examples
If you're building React/Angular dashboards on top of Dataverse, this pattern matters.
Frontend meets enterprise security.
http://mytrial365.com/2026/04/16/connecting-to-dataverse-from-a-single-page-app-spa-using-msal-cors/
🚀 Part 4 is live: Multi-Tenant S2S for Dataverse (SaaS/ISV Architecture)
Building for multiple customers? One tenant is easy. Many tenants is architecture.
🔐 Admin consent flow
🏢 Application Users per environment
🌍 Tenant isolation
⚙️ Dynamic authority handling
If you’re building AppSource-ready solutions, this is the pattern you must understand.
Multi-tenant isn’t just auth. It’s responsibility.
🚀 Part 3 is live: Server-to-Server (S2S) Authentication in Dataverse
No login prompts.
No user context.
Pure application identity.
In this post, I break down:
🔐 Application Users
⚙️ Client Secret vs Certificate
☁️ Azure Function implementation
🧠 Single-tenant architecture explained
If you're building real enterprise integrations, S2S is non-negotiable.
Architecture starts with authentication.
Part 2 of my Dataverse connection series is live.
This one goes deep into modern .NET authentication using ServiceClient OAuth setup, connection strings, token lifecycle, delegated vs app-only context, and real C# examples.
If you're building console tools, Azure Functions, or DevOps utilities for Dataverse, this is the pattern you should master.
Clean architecture starts with correct authentication.
New blog series: Connecting to Dataverse the right way.
OAuth, S2S, SPA, multi-tenant real scenarios, real code, clear decisions.
Stop guessing. Start architecting.
http://mytrial365.com/2026/03/19/connecting-to-dataverse-choosing-the-right-authentication-strategy/
🕵️♂️ Deleted or... just disappeared?
In Part 4 of my Dataverse Bulk Delete series, I unpack how to:
✅ Track job status
🧾 Review success/failure logs
🐞 Debug record deletion failures
Your deletion jobs deserve better than blind trust.
