ARAnil Ramisettyinenterprise-crm-insights.hashnode.dev·Aug 11 · 9 min readEnterprise CRM Insights #2: Plugin vs. Power Automate — A Practical Decision FrameworkIn my previous article, Enterprise CRM Insights #1, I mentioned that one of the common architecture decisions in Dynamics 365 projects is choosing the right tool for the problem. One question I have c00
SBSyed Bilal Ahmedinsyedbilal365.hashnode.dev·Aug 6 · 7 min readHow to Convert a Code App Into a PCF ControlPart 6 of the PCF Build-Alongs series. Somewhere between "I built a Code App" and "the users want it embedded in a form", you realise you built the wrong thing. Or, more accurately, you built the righ00
ARAnil Ramisettyinenterprise-crm-insights.hashnode.dev·Jul 31 · 5 min readEnterprise CRM Insights #1: Seven Principles for Building Successful Enterprise Dynamics 365 SolutionsWelcome to Enterprise CRM Insights, a publication where I share practical lessons, architecture patterns, implementation best practices, and delivery experiences from enterprise Customer Engagement pr00
MIMyData Insightsinmydatainsights-blogs.hashnode.dev·Jul 24 · 11 min readYour CRM Tracks the Pipeline. It Can't Tell You What You Actually Made. A Dubai brokerage can tell you, to the hour, how many leads it took last week and which agent sits top of the board. Ask how much of last quarter’s commission has actually reached the bank, and the pr00
VNVinit Nairinvinitnair.hashnode.dev·Jul 17 · 6 min readTeams Telephony Manager: A Real-World, Open-Source Power Apps Code AppTL;DR Code apps are the new pro-code way to build on Power Platform (React and TypeScript running on Dataverse), and they are genuinely powerful. But when I was learning them, I wanted one thing I cou00
SSapotaCorpinsapotacorpvn.hashnode.dev·Jul 12 · 15 min readPower Apps for a driving school: weekly to yearly KPI reportsClient: Japanese driving school chain (anonymized per agreement) Timeline: 6-month rebuild from the legacy stack, ongoing iteration since Team: 6 engineers including 2 from Sapota's Power Platform tea00
SSapotaCorpinsapotacorpvn.hashnode.dev·Jul 12 · 6 min readPower Platform requirements: the non-functional ones decide the architectureThe Power Platform projects that go wrong at go-live usually did the obvious half of requirements gathering well. Someone sat with the business, wrote down everything the solution had to do, the scree00
SSapotaCorpinsapotacorpvn.hashnode.dev·Jul 12 · 6 min readFit-gap to component selection: matching requirements to the right Power Platform piecePower Platform is not one product, it is a suite, and the most consequential thing an architect does on a project is decide which piece of that suite each requirement belongs to. Canvas apps, model-dr00
SSapotaCorpinsapotacorpvn.hashnode.dev·Jul 12 · 6 min readBusiness continuity for Power Platform: what Microsoft covers and what you still ownAsk most teams what their business-continuity plan for a Power Platform solution is, and the answer is some version of "it's in the cloud, Microsoft handles it." That answer is half right, which is wh00
SSapotaCorpinsapotacorpvn.hashnode.dev·Jul 12 · 10 min readPower Automate at Scale: Survival Patterns When Flows Get BigPower Automate gets you moving in an afternoon, then quietly punishes you six months later when the same solution holds dozens of flows that nobody can reason about. We learned this on a KPI reporting00