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. #PowerAutomate #PowerPlatform

if i look back, i am lost
ojovivo

Origami Around
DEAR READER
dirt enthusiast
todays bird
Cosmic Funnies
tumblr dot com
Show & Tell

titsay
I'd rather be in outer space 🛸
Aqua Utopia|海の底で記憶を紡ぐ

ellievsbear

No title available
Monterey Bay Aquarium
Not today Justin
Three Goblin Art

祝日 / Permanent Vacation

PR's Tumblrdome
RMH

seen from Austria

seen from Türkiye
seen from United States
seen from United States
seen from United Kingdom
seen from Spain

seen from Türkiye
seen from Türkiye

seen from United States
seen from Germany

seen from United States
seen from United Kingdom

seen from United States
seen from Germany
seen from United Kingdom

seen from South Africa
seen from United States

seen from Germany

seen from Malaysia

seen from Algeria
@kailashr2k
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. #PowerAutomate #PowerPlatform
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. #PowerAutomate #PowerPlatform
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 🧵 #PowerAutomate #PowerPlatform
🔄 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.
🚀 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 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.
🕵️♂️ 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. #PowerPlatform #Dataverse #SystemJobs #AuditReady
📦 Not all data is trash. In Part 3 of my Bulk Delete series, I dive into retention-aware strategies when NOT to delete, how to archive, and staying compliant with long-term data. Because sometimes, keeping it is the smart move. #PowerPlatform #Dataverse #Compliance #DataGovernance
💥 Automate the Clean Slate. In Part 2 of my Dataverse Bulk Delete series, we go beyond the basics: 🗓️ Schedule recurring jobs 📊 Monitor success/failure 🛠️ SDK + UI + real scenarios #PowerPlatform #Dataverse #Dynamics365 #PowerApps #CleanupOps
In Part 1 of my Bulk Delete series, I break down how to automate large-scale cleanups safely using the built-in Bulk Delete feature. ✅ Background jobs ✅ Scheduling ✅ SDK + Web API examples ✅ Real-world use case #PowerPlatform #Dataverse #Dynamics365 #PowerApps #ProDev
Your search is only as smart as your analyzer. In Part 6 of my Power Apps Search series, I show how to define custom search analyzers to control indexing and precision matching. Perfect for multilingual, code-heavy apps.
🔍 Your Power Apps search is only as good as your index. In Part 5 of the Dataverse Search series, I show how to monitor search health using the Statistics API with real examples and pro tips for debugging stale or broken search.
🔤 Autocomplete in Power Apps? Absolutely. Part 4 of my Dataverse Search Series explores the Autocomplete API perfect for predictive UX and smart typing. We cover: ✅ Partial-term matching ✅ Web API request/response ✅ When to use Autocomplete vs Suggest