Time Entry Delegation (Preview) in Microsoft Dynamics 365 Project Operations
IntroductionIn this blog, I’m going to talk about another productivity-boosting enhancement in Dynamics 365 Project Operations, the Time Entry Delegation (Preview) feature. This feature, released as a production-ready preview on September 24, 2025, allows a resource to log, modify, or submit time entries on behalf of another user for a limited duration. In simple words, if someone is on leave or unavailable, another trusted team member (delegate) can take over their time entry responsibilities without disturbing project timelines. Problem Statement In traditional setups, only the assigned resources could log or submit their time entries.This created challenges when: These scenarios resulted in missing time entries, delayed invoicing, and reporting inconsistencies. To address this gap, Microsoft has introduced the Time Entry Delegation feature. UPDATE: The Time Entry Delegation feature enables a resource (called the delegator) to temporarily assign another user (called the delegate) who can: Enabling Time Entry Delegation (Preview) Enabling the Feature Once activated, a new menu item called “Delegates (Production Ready Preview)” will appear under the My Work section in both the Project Operations and Team Member apps. Setting Up a Delegate After enabling the feature, setting up a delegate is simple: Once saved: Other Views Available Logging Time as a Delegate When you are assigned as a delegate, you can log and manage time entries for another user: Example: Let’s say William is on leave from October 7th to 11th.He assigns John as his delegate for that period. Now, during these dates, John can: After October 11th, delegation automatically ends, and Priya regains full control of her time entries. Time Entry Experience for Delegates When delegation is active, a few changes appear in the Time Entry form: Other fields (like Project, Task, and Role) automatically adjust based on the delegator’s assignments. This ensures that the delegate only logs time on projects or tasks relevant to the original user. Note: These changes apply only during weeks when a delegate relationship exists. Outside of delegation weeks, time entry behavior remains normal. Tracking Time Entries Logged by Delegates Both the delegate and delegator have dedicated views: For Delegates For Delegators Audit Trail for Delegated Time Entries During the preview phase, Project Operations tracks delegated actions using two key fields: Current Limitations Conclusion The Time Entry Delegation (Preview) feature is a major productivity booster for organizations using Dynamics 365 Project Operations. It brings flexibility to resource management by allowing temporary delegation of time logging and submission responsibilities — ensuring that project timelines, invoices remain accurate and up-to-date, even during employee absences. Thank you, Kalyani for your valuable inputs to these blogs!
Prompt Columns in Dataverse
Introduction In this blog, I’m going to share about a new capability in the Power Platform: The Prompt Column (Preview) in Dataverse. This feature brings the power of generative AI directly into your data tables, allowing makers to create AI-driven text outputs based on other columns within the same record. Traditionally, if you wanted to generate summaries, categorize records, or draft responses, you’d rely on Power Automate flows, plugins, or external AI connectors. That meant extra steps, more configurations. With the Prompt Column, you can embed intelligence directly in your data model. You define a prompt a natural language instruction and the system dynamically generate text output based on the values in other columns of the record. Problem Statement One of the challenges in most business apps is context generation. Data often exists in isolation descriptions, titles, and notes are stored separately, and users must interpret meaning manually. This disconnect means that insights are locked behind manual work or external processes, slowing down decision-making and reducing the real-time value of your data. Solution The Prompt Column (Preview) helps bridge this gap by letting you define AI prompts directly within Dataverse. Using natural language, you can instruct the system to generate text based on other columns — no flow, plugin, or external integration required. For example, you can create a prompt like: “Summarize the case title and description in 3 bullet points.” and the column will automatically produce an AI-generated summary whenever the record is viewed or refreshed. This makes your data tables smarter and your forms more informative — enabling use cases such as: Steps to Create and Test a Prompt Column in Dataverse Define the PromptWrite your natural language instruction Add Input ColumnsSelect which columns should be used as input (like Title, Description, Priority, etc.) You can always filter the attributes as well so have more precise data according to your needs. Save and Add to FormAdd the prompt column to a form in your model-driven app so you can visualize the output. Test the OutputOpen or create a record, populate your input fields, and let the prompt generate text automatically. You can always play with the available models and see which suits best. Refine or IterateAdjust your prompt for tone, detail, or format. For example, you can make it formal, concise, or bullet-style depending on your use case. So that’s pretty much about it , for now the prompt column feature only gives you text as the default data type. You can further play around with the feature and always try new things eg: I tried generating a Json format with some attributes in my table which could be used in power automate flows or further processing Conclusion: As this feature matures, it’s likely to evolve beyond record-level prompts, potentially opening doors to contextual AI summaries across relationships and tables. For now, it’s a great opportunity to experiment, learn, and rethink how you make your data tell its own story. Thank you Aslin, for your valuable inputs to this blog!
Using the Dataverse MCP Server in Copilot Studio
Introduction In this blog, I’ll share insights about an exciting advancement in Copilot Studio, the integration of the Dataverse MCP (Model Context Protocol) Server. This feature provides a seamless bridge between Microsoft Dataverse and Copilot Studio, enabling developers and makers to build intelligent copilots that can directly interact with enterprise data stored in Dataverse. Let’s dive into what this means, why it matters, and how you can use it effectively. Public preview: October 2025 (Microsoft Dataverse 2025 release wave 2)General availability: Planned for March 2026 Problem Statement Until now, connecting Dataverse data with Copilot Studio required multiple connectors, authentication configurations, or manual API setups. Makers had to define custom plugins, write Power Automate flows, or expose APIs to interact with Dataverse tables. This created friction for business users and slowed down the delivery process for conversational bots that needed to fetch, interpret, and act on business data. The challenge for us is: How can we enable Copilot Studio agents to natively access Dataverse resources and execute operations securely and efficiently, without coding overhead or complex integration setups, while ensuring tools and resources stay dynamically updated? Solution: Dataverse MCP Server Integration for Copilot Studio Microsoft has introduced the Dataverse MCP Server as part of the new Copilot Studio extensibility model. This integration allows Copilot Studio to use Microsoft Dataverse as a native data backbone using the MCP (Model Context Protocol) protocol for secure and intelligent data exchange. The MCP Server acts as a runtime data gateway, enabling Copilot agents to interact with Dataverse entities such as accounts, leads, contacts, projects, and custom tables directly within Copilot Studio dialogs. Key capabilities of this new integration include: How to Use the Dataverse MCP Server in Copilot Studio? Prerequisite: Enable “Dataverse Model Context Protocol” in Power Platform. Open admin.powerplatform.microsoft.com and navigate to your environment. Go to Settings. Expand Product dropdown and select Features. Find and enable “Enable Dataverse Model Context Protocol” and click on Save button located at the bottom right corner. Open Copilot Studio: This way we can easily setup MCP server for our agent and allow our agent to perform Dataverse actions. Considerations and Limitations Conclusion The Dataverse MCP Server integration in Copilot Studio represents a major leap in enterprise-grade AI and data connectivity. By connecting Copilot logic directly to Dataverse, makers can now build intelligent, context-aware copilots that act on live organizational data all without writing code or managing connectors. The dynamic nature of MCP ensures that as tools and resources are updated or removed on the server, Copilot Studio automatically reflects these changes, keeping your agents current and reliable. As this feature evolves toward general availability, expect deeper support for multi-environment management, cross-source integration, and advanced AI reasoning on relational data. If you’re working in the Power Platform or Dynamics 365 ecosystem, now is the perfect time to explore how Dataverse or other MCP Server can enhance your Copilot experiences. Thank you, Darish for your valuable inputs to this blog!
Time Entry Calendar Interface (Preview) in Project Operations
IntroductionIn this blog, I’m going to share about Time Entry Calendar interface (Preview) for Dynamics 365 Project Operations (version 4.141.0.X or later). In this feature users will gain a more visual and intuitive way to log, edit, and manage time entries—far beyond what the classic grid offered. Public preview: May 30, 2025; General availability: Sep 2025 Problem Statement In the existing setup, users rely heavily on the Time Entry Grid to input and review hours. Teams often face challenges such as: These limitations slow down task logging, increase errors, for managers and team members. UPDATE: Time Entry Calendar (Preview) To address these challenges, Microsoft has introduced the Time Entry Calendar, a calendar-style interface integrated into Project Operations. Key features include: How It Works: Enabling the Feature Viewing Entries Creating Entries You can also copy entries using Ctrl + C / Ctrl + V. Pasted entries carry most fields (project, task, description), while the duration adjusts based on where they’re pasted. Editing Entries Submitting / Recalling / Deleting UI Use the view picker to toggle between Daily, Weekly, Monthly, or Agenda views. Use the date Icon to switch the dates Use the refresh icon to refresh the page Submit all the records directly by clicking on submit button Tracking & Filtering EXAMPLE: Sarah is a consultant who logs time across multiple projects. Before vs After: Time Entry Experience Aspect Before (Grid View) After (Calendar View – Preview) User Interface Tabular grid, requires manual entry for each day/task Visual calendar (Daily/Weekly/Monthly/Agenda views) Ease of Entry Manual typing of hours -> repetitive and error-prone Click, drag, resize, or copy entries directly on calendar Status Visibility Must open each entry to check Draft/Submitted/Approved Color-coded (Yellow = Draft/Returned, Blue = Submitted, Green = Approved) Editing Flexibility Open form -> change values -> save Drag-and-drop to new time slot, resize, or double-click to edit Tracking Progress Requires reports/dashboards Built-in charts for logged vs. target hours, daily/weekly trends Clarity Hard to spot missing/duplicated entries Tooltip details make it clear immediately Productivity Impact Slower, manual, error-prone Faster, intuitive, reduces errors, boosts efficiency Conclusion The Time Entry Calendar (Preview) brings a fresh, user-friendly approach to logging and managing time in Project Operations. While still in preview, it promises to enhance productivity and clarity by enabling users to visualize their hours, correct entries quickly, and remain aligned with targets—all within a single, intuitive interface. Thank you, Kalyani for your valuable inputs to this blog!
Generative Pages in Model-Driven Apps
Introduction In this blog, I’m going to share details regarding a newly introduced feature for model-driven apps called Generative Pages. This feature lets developers design functional, modern pages for model-driven apps simply by describing their requirements in plain language. Here’s a hands-on look at this feature using Microsoft’s latest updates and a walkthrough based on real experience. Public preview: May 16, 2025 (rollout phased through 2025 Wave 1 update) General availability: Not yet available (planned for March 2026) Problem Statement Traditionally, creating new custom pages in model-driven apps was time-consuming. Designers and developers had to manually think about the design, add each control/container, configure Dataverse sources, and fine-tune layouts, often requiring coding expertise and hours of iteration. This complexity created a barrier for business users and slowed the delivery of modern, dynamic business apps. The challenge is clear: how do we reduce the complexity of creating custom pages manually, investing a lot of time for design and development? Solution: Generative Pages in Model Driven Apps editor Microsoft has introduced Generative pages, a feature in Power Apps platform within the model-driven app editor. Generative Pages offer an AI-powered approach that leverages Copilot for page creation. Instead of manual configuration, users can describe their requirements in natural, everyday language. The App Agent for Generative Pages interprets these instructions, references relevant Dataverse tables, and produces a clean UI complete with filters, dashboards, forms, and fully integrated code. Key benefits of this new feature include: How to use Generative Pages? Updated code preview: Cleaner design. Updated code preview: Popup for “New Event” button. Updated code preview: Dashboard view added. After finalizing the page generation, you can save and publish and can edit it anytime in future if needed. Considerations and Limitations As this is an early preview, a few boundaries to keep in mind: Conclusion Generative Pages in Power Apps represent a dramatic leap forward in enterprise app building. With the power of natural language, AI-driven layouts, and direct ties to Microsoft Dataverse, business users and developers can deliver tailored solutions quite faster and focus on other tasks. As this feature matures, expect even more flexibility, data options, and co-authoring capabilities. If you are working in the D365 or Power Platform space, now’s the perfect time to try Generative Pages and master the ability to create low-code, AI-powered business app in no time. Thank you, Darish for your inputs to this blog.
How to generate Model-Driven and Canvas Apps with Copilot
Introduction In this blog, I’m going to share about an exciting capability in the Power Platform: generating Model-Driven and Canvas Apps with Copilot. Traditionally, creating apps required a lot of setup defining tables, building forms, and wiring up relationships before you could even start testing your idea. This process often slowed down makers who wanted to quickly translate business needs into working solutions. With Copilot, Microsoft has introduced a smarter way to begin. Instead of starting from scratch, you can describe your app in plain language, and Copilot will generate the core structure tables, forms, views, and layouts for you. It’s not meant to replace customization, but it gives you a strong starting point so you can spend less time on repetitive setup and more time shaping the features that matter most to your business. Problem Statement One of the biggest challenges with Model-Driven and Canvas Apps is the amount of upfront work required before you even have something usable. You need to define tables, set up relationships, and design forms and views. While this structure is powerful, it often slows down innovation. For organizations that want to quickly test ideas and turn them into business solutions, this initial setup can feel like a hurdle rather than a starting point. Solution Copilot helps bridge that gap. By using natural language, you can describe the kind of app you need, and Copilot will generate the basic structure for you. It cuts down the setup effort and lets you jump straight into refining and extending your app. Steps to Generate a Model-Driven App Using Copilot Step 1: Navigate to the Maker PortalGo to make.powerapps.com. Select Create → Start with Data. Step 2: Describe Your AppYou will be prompted to describe your app in around 200 characters. For example, try this prompt: “Create a model-driven app for managing projects, tasks, and approvals with entities for Projects, Team Members, Status, and automated workflows for notifications and reporting.” Copilot will generate a draft app plan for you. Step 3: Refine the PlanAfter the first iteration, you can keep adding details in natural language to refine the entities, relationships, and features. For instance, you might add requirements for resources, deadlines. Step 4: Save and Choose Your App TypeOnce satisfied with the generated plan, select Save and Open App. The dropdown gives you an option to choose between a Canvas App and a Model-Driven App. For this walkthrough, we’ll select a Model-Driven App. Step 5: Review and ExtendYour model-driven app is now ready. While Copilot generates the core entities and relationships, it might not cover every required field or customization. You can easily extend the app by: Final Thoughts Copilot doesn’t replace the need for thoughtful design, but it dramatically reduces the time and effort required to get started. Instead of spending hours on setup, makers can focus on building value-driven features, refining user experiences, and aligning apps with organizational goals. As the feature matures, it will become an assistant in the low-code toolkit making app creation faster, smarter, and more accessible for everyone. In the meantime, makers are encouraged to experiment with its limits and capabilities to fully understand its potential. Thank you, Aslin for your inputs to this blog.