The Solzet blog answers the practical questions mid-market companies and Microsoft partners ask before, during and after a Dynamics 365 or Power Platform project. Articles cover Dynamics 365 Customer Engagement, Field Service, Power Apps, Power Automate, PCF controls and Dataverse, from choosing a partner and migrating from Salesforce to rescuing an implementation that went wrong. Each post leads with a direct answer and closes with a short summary and common questions. They are written by the consultants who deliver this work, drawing on 8+ years of hands-on projects. Where Microsoft licensing does not fit, the articles point to the alternative: a custom-built CRM you own outright.
How mid-market teams move business data out of spreadsheets into Dataverse: inventory, data modelling, alternate keys, clean imports, and retiring the files.
Read more →Dynamics 365 is not always the right CRM. How to spot a poor fit, when Power Platform is enough, and when a custom-built CRM gives you full control instead.
Read more →Sales ignoring Dynamics lead scores? Rebuild from closed-won history, use a small rule-based score sales can read, publish the rules, validate before routing.
Read more →Omnichannel numbers disagree with store and web data, or first contact resolution looks too good? Freeze the records, define each metric, rebuild one figure.
Read more →Digitising customer forms, invoices and handwritten notes for an audit? Capture new data at source, extract old documents with AI Builder, verify every field.
Read more →Marketing sends from Dynamics 365 got invoices blocked? Pause sends, split transactional mail, check SPF, DKIM and DMARC alignment, warm up to engaged only.
Read more →Customers double booking a slot? Enforce one slot record with a server-side uniqueness rule, then pick Forms and Dataverse, Power Pages or a custom portal.
Read more →Cannot forecast renewals because Dynamics subscription data is wrong? Give finance a reconciled number with an exclusion list, then fix the renewal data model.
Read more →No server-side sync in Dynamics 365? Use a Purview eDiscovery export for the audit, then a shared mailbox flow that matches records and dedupes on message ID.
Read more →CSAT scores nobody believes? Dispatch surveys by rule from a system account, pick recipients from case data, lock responses and keep a full audit history.
Read more →Old fixed-price Dynamics 365 contracts losing margin? Rebuild delivered effort against scope, add a change-control gate and rethink delivery cost first.
Read more →Quarter-end survey report due? Check Customer Voice entitlement, or use Microsoft Forms, a flow and Dataverse, then merge five teams into one defensible view.
Read more →Locked in to an outsourced Dynamics 365 team only they understand? Freeze change, demand runbooks, own credentials, get an independent review, then transition.
Read more →Your only Dynamics 365 administrator is leaving? Export solutions, flows, roles and plug-ins, reassign their connections, record walkthroughs and test a change.
Read more →Complaints in a shared mailbox and spreadsheet? What auditors test, interim controls that make the mailbox defensible, and a traceable case system design.
Read more →Customer portal barely connected to Dynamics 365 and clients threatening to leave? The assessment that decides fix or replace, and when each route is right.
Read more →Dynamics 365 data quality breaking invoicing and compliance? Scope to the fields that matter, profile with Power Query, fix at source, then clean in batches.
Read more →Power App holding sensitive HR data that too many people can see? Contain sharing and anonymous links, keep the logs, then secure the data source itself.
Read more →Large, messy CRM list and one generic newsletter? Segment by behaviour first, suppress instead of deleting, dedupe on email and enrich only the fields you need.
Read more →Missing records before an audit? Rebuild from surviving evidence, label it reconstructed, keep a register of source and confidence, and disclose the gap.
Read more →Billing errors from your CRM driving clients away? Stop wrong invoices today, size the error population, find the root cause and add controls that stop repeats.
Read more →Undocumented CRM to finance integration blocking quarter-end close? Reconcile the numbers first, then trace it from the finance side and replace it in stages.
Read more →The one person who runs your payment or invoicing app is leaving? Hand over access, source, runbooks and a payment fallback, then prove it before they go.
Read more →Every team keeps its own customer spreadsheet? Publish one authoritative record, match on deterministic keys, reconcile copies and move teams over in phases.
Read more →Frontline rollout failed? Quarantine bad data, observe two contrasting sites, rebuild one as the reference, then relaunch site by site on measurable terms.
Read more →Business-critical system crashing daily? The first 48 hours in order, then triage that decides stabilise, remediate or replace, on evidence rather than panic.
Read more →A Dynamics developer overstated their skills and left a failed migration before an audit? Scope access, back up, inventory every change, then plan the repair.
Read more →Dynamics dashboard numbers do not match finance? Walk one metric from source record to report cell, check the five usual causes, then fix it in the data model.
Read more →Audit data scattered across old Excel files? Freeze the sources, agree each metric in writing, stage with row-level checks and publish one figure with lineage.
Read more →Inventory optimization in Dynamics 365 Supply Chain Management: coverage settings, safety stock, ABC classes, van stock and cycle counts most plants skip.
Read more →The five Power BI reports a plant manager actually uses - OEE, scrap Pareto, downtime, OTIF, and maintenance backlog - and how to model them on Dataverse.
Read more →How a mid-market manufacturer should evaluate a Dynamics 365 partner: the ALM, Field Service, ERP integration and licensing questions that predict delivery.
Read more →A 10 question buyer checklist for choosing a Dynamics 365 partner in Armenia, plus the Dataverse decisions you cannot undo and who really owns the build.
Read more →How a Dynamics 365 rescue really works: naming the root cause before fixing anything, plus a full walkthrough of Customer Service unified routing setup.
Read more →What a Dynamics 365 rescue and takeover involves: reading a half-built environment, stabilizing it, fixing Field Service scheduling and moving it forward.
Read more →What Yerevan-based Dynamics 365 and Power Platform delivery looks like: nearshore time zones, certified engineers, project rescue and a due-diligence checklist.
Read more →What "an experienced team we can plug in" really means for Power Apps: how a nearshore Center of Excellence joins your project without a long ramp-up.
Read more →Getting a Kanban board into Dynamics 365: install a third-party AppSource app or build a custom PCF control, and how to tell which one your team really needs.
Read more →The Dynamics 365 customizations that break most often, how to fix them, and why searching for a training provider like Dynamics Edge is often the wrong move.
Read more →Migrating from Salesforce to Dynamics 365: map objects to Dataverse, rebuild Apex and Flow logic, migrate in reconciled phases, and dual run before cutover.
Read more →How Power Apps replaces shop-floor paper forms: quality checks, downtime logs, and inspections that validate at capture, work offline, and land in Dataverse.
Read more →Business Central vs Finance and Operations for any industry: fit rules for manufacturers, distributors, retail and project firms, localization, licensing.
Read more →How Power Automate approval flows take the email and spreadsheet drag out of mid-market finance: invoice, PO and expense sign-offs that route and escalate.
Read more →D365 Field Service implementations fail on data, scheduling, and adoption - not the software. Why mid-market projects stall, and how to get the rollout right.
Read more →Mid-market companies already pay for Power Platform through Microsoft 365. Here is how to start using Power Apps, Power Automate, and Power Pages today.
Read more →Why Microsoft Partners subcontract Dynamics 365 delivery - bench gaps, specialized skills, cost - and how to structure agreements, quality, and IP correctly.
Read more →Dispatching field technicians over WhatsApp feels free but quietly costs you in scheduling chaos, lost documentation, and no analytics. Here is the real price.
Read more →A practical overview of Dynamics 365 Customer Engagement: the apps it includes, what Microsoft Dataverse is and why it matters, and when CE fits your business.
Read more →Microsoft Dynamics 365 Customer Engagement (including Sales, Customer Service and Field Service), the Power Platform (Power Apps, Power Automate, Power BI and Dataverse), PCF controls, and how Microsoft partners work with delivery teams. Articles range from choosing a partner and migrating from Salesforce to rescuing an implementation that went wrong, and they point to custom CRM development where Microsoft licensing does not fit.
The Solzet consulting team: the same senior consultants who deliver the projects the articles describe. The Customer Engagement and Power Platform articles come from 8+ years of hands-on delivery rather than from marketing briefs, which is why they name trade-offs and failure modes instead of only the happy path.
Yes. Solzet implements Dynamics 365 Business Central and Finance and Operations alongside Customer Engagement and Power Platform, and the blog covers them too: choosing between Business Central and Finance and Operations, supply chain questions, and the integration between CRM and ERP.
Not only. We recommend the right solution: Dynamics 365 (Customer Engagement, Business Central or Finance and Operations), Power Platform, or a custom-built CRM. One team for CRM, ERP and the integration between them. Articles about the Microsoft platform link to custom CRM development for organizations that need CRM capabilities without Microsoft licensing.
Yes. Solzet provides white-label subcontracting for Microsoft partners, and the Microsoft Partners articles explain how partners bring in an experienced Dynamics 365 or Power Platform team and how to structure that work so it goes well for the end client.
Yes. Use the enquiry form at the foot of this page and describe what you are trying to solve and what you run today. A senior consultant replies within one business day with a recommendation, whether that is Dynamics 365 (Customer Engagement, Business Central or Finance and Operations), Power Platform or a custom-built CRM.
We recommend the right solution: Dynamics 365 (Customer Engagement, Business Central or Finance and Operations), Power Platform, or a custom-built CRM. One team for CRM, ERP and the integration between them.
Implementation, extension and rescue of Dynamics 365 Customer Engagement.
Power Apps, Power Automate, Power Pages and Dataverse solutions.
Custom TypeScript and React controls that run natively in model-driven apps.
Senior Dynamics 365 and Power Platform delivery for Microsoft partners.
A CRM you own outright, for organizations that need CRM without Microsoft licensing.
Tell us what you are working on. A senior consultant replies within one business day with a recommendation, whether that is Dynamics 365 (Customer Engagement, Business Central or Finance and Operations), Power Platform, or a custom-built CRM.