Posts

Showing posts with the label Dynamics365

Behind the Names: Unlocking Schema and Logical Names in Dataverse

Image
Schema and Logical Names in Dataverse form the backbone of how data is structured, stored, and referenced within the platform. The Schema Name is a system-level, immutable identifier created when a table or column is generated; it is mainly used by developers, plugins, integrations, and API calls. It follows a strict format (prefix + name) and does not change even if the display name changes, ensuring long-term stability for solutions and custom code. The Logical Name , on the other hand, is the programmatic name Dataverse uses internally and externally when accessing data through the Web API, SDK, Power Automate, or Power Apps. Logical names are unique and aligned to the physical storage in the Dataverse database. While schema names provide structure and a consistent metadata definition, logical names enable efficient data operations and integration. Together, they create a reliable separation between user-friendly labels and system-driven identifiers, ensuring stability, consistency...

Demystifying Clusters in Power Platform: What Architects and Developers Must Know

Image
When working with Microsoft Power Platform—especially Dataverse—you’ve probably seen terms like Cluster Geo Name or Cluster URI Suffix in your environment diagnostics. But what exactly is a cluster , and why should architects and developers care about it? Let’s break it down. What is a Cluster in Power Platform? A Cluster in Power Platform is a logical and geographical grouping of Dataverse instances . Think of it as: A container for environments (Dev, Test, Prod) Hosted in a specific Azure region (EU, US, Asia Pacific) Designed for data residency, compliance, and performance Every Dataverse environment you create is part of a cluster, which Microsoft manages behind the scenes for scaling and governance. Why Do Clusters Exist? Microsoft uses clusters to: Ensure Data Residency Keep customer data within the selected geography (important for GDPR, HIPAA). Optimize Performance Place environments closer to end-users for low latency API calls. Provide Compliance Boundarie...

Study guide for Exam MB-280: Microsoft Dynamics 365 Customer Experience Analyst

Image
  Skills at a glance  Implement Dynamics 365 Sales (25–30%) Configure and customize Dataverse and model-driven apps (25–30%) Implement the Dynamics 365 App for Outlook (10–15%) Implement security and customizations in Dynamics 365 Sales (10–15%) Demonstrate Dynamics 365 Customer Insights capabilities (10–15%) Extend and enhance Dynamics 365 Sales capabilities (5–10%) Implement Dynamics 365 Sales (25–30%) Configure core functionality of Dynamics 365 Sales Evaluate predictive lead and opportunity scoring model performance Configure predictive lead and opportunity scoring models Enable and configure predictive lead and opportunity scoring Configure the lead qualification experience Configure the opportunity pipeline view Interpret the Sales Pipeline chart Interpret the opportunity pipeline view Configure and deploy the Sales mobile app Enable email validation Set up the product catalog Configure product catalog settings Differentiate the product catalog components Manage the prod...