Invoice Schedule Types in Project Operations

Blog Post coming on 6th April 2026!

Thank you!

Time Entry Calendar in Project Operations

If you have been used to doing Time Entries daily on the classic Time Entry grid and that has been a habit for quite some time, you might not realize that it is slower and inefficient to do, just because you got used to it now.
So, here’s Time Entry calendar view which is better way to visualize and do Time Entries! This is in Preview as of the day of writing this post.

Enable Time Entry Calendar View

Here’s how you can turn on your Time Entry Calendar from Project Operations’ Settings

  1. Navigate to Settings Area in Project Operations Model-Driven app.


  2. Then drop down form Features to find the Time Entry Calendar listed.


  3. Click on it to turn it on. It’ll ask for confirmation, it ask describes what it does.


How Time Entry Calendar works?

Here’s how Time Entry Calendar feature works when you want to do Time Entries.

  1. Now when you navigate to the Time Entries from My Work (or wherever you have put it), you’ll see this new option in My Work called as Time Entry Calendar, while you existing Time Entry section still exists as is.

  2. When it loads, you can see the Time Entries now appear like how allocations appear on your Schedule Board, gives you a better way to visualize Time Entries to be done and and most importantly, select the Time for the Time Entry.
    You can visualize Daily, Weekly and Monthly.


  3. You can even click on the Time you want to make Time Entry on and the window pane will let you drill down to the Task level on the Project which you want to make Time Entry on.

Hope this was useful!

Thank you!

Hide Resources from Schedule Board in Project Operations [Quick Tip]

In case you want a Resource to not be visible for Resource Managers to find and book, here’s how you can choose to hide them without having to work through filters

Default Behavior

Here’s what the default behavior will work for all Resource where you see a Resource like below – We are considering the example “Priyesh Wagh” as a Bookable Resource.


Now, let’s hide Priyesh Wagh as a Bookable Resource from the Schedule Board.

Hide Bookable Resources from Schedule Board

Fortunately, here’s how you hide Bookable Resources from appearing on the Schedule Board-

  1. Go to Resources table in the Resources area in the Project Operations sitemap. And look for the Resource you want to hide.

  2. And, go to the Scheduling tab and look for the below highlighted option called ‘Display On Schedule Board‘ which would be set to Yes. Set it to No and then save the record.


  3. Once this is set to No, then go back and Refresh the Schedule Board and Resource would be hidden. Even if you find the Resource, you won’t be able to find it.


Hope this was useful!

Thank you!

Power Platform Tools for Visual Studio

Here’s how you can quickly deploy and debug Dynamics 365 CRM plugins using Power Platforms Tools in Visual Studio

This is the first post in the series and once complete setting up Power Platform Tools for Visual Studio, I’ll follow up with writing and deploying C# CRM Plugins through Power Platform Tools for Visual Studio!

Let’s setup Power Platform Tools for Visual Studio first!

Getting Power Platform Tools in Visual Studio

Here’s how you can configure Power Platform Tools in Visual Studio from the Marketplace –

  1. In your Visual Studio, under Extensions, click on Manage Extensions.

  2. Then, search for Power Platform Tools and you’ll find on in the top few results itself which you will be able to identify as highlighted below.
    Click to install the “Power Platform Tools for VS 2022“

  3. You’ll need to close Visual Studio for the installation to be proceed.

  4. Then, it’ll continue as a VSIX Installer and continue to install this extension for your VS.

  5. And this will be completed in a few moments.

  6. Once done, when you open Visual Studio back again, you’ll find “Connect to Dataverse” under Tools section in Visual Studio

  7. It’ll ask you to authenticate into your Dataverse environment. This doesn’t work with accounts using MFA – so for this demonstration, I turned off MFA temporarily for my trial environment.

  8. Then, I was asked to select the environment within the tenant.

  9. Now, I was asked to choose the Solution within the selected environment.


  10. Now, I could see all the Tables expanded in the Power Platform Explorer view.

  11. When you minimize, this is what you’ll see. You’ll see all items available to work with.


Next, I’ll demonstrate on registering a Plugin Assembly from Visual Studio Tools and registering a plugin. Watch this space!

Hope this was useful!

Thank you!

Cards in Power Apps

Cards in Power Apps can get you to send Adaptive Cards in Teams chats or channels without having to leave Power Platform to make your card!

Yes, till recently I was having a hard time to make an Adaptive Card in the Adaptive Cards Designer which is outside of the context of Dynamics/Dataverse and then embed it into Flow to be sent to a User – until Cards in Power Apps came along!

Let’s see how we can get started with the same and create our first Card and send in a Teams Chat!

Create a Card in Power Apps Maker Portal

Given you have appropriate access to create and view Cards, here’s how you can create your Card in Power Apps Maker portal –

  1. Navigate to Power Apps Maker Portal (https://make.powerapps.com/) and select the right environment with Dataverse in which you want to create your Cards.

  2. When you click on + New Card, Cards will ask you to name it and add a description.

  3. And once you create – you’ll be taken to the Card Studio.

  4. One the left hand side, you can see the menu which you can identify what the Card can be configured to do.

  5. To keep the function of the Card example, simple – I’m only displaying the logged in user name on click of a button.


  6. Notice that on the right hand side, you have different ways to deploy this Card – like in a Teams Chat.

  7. When in Play Mode, you’ll get to use the Card as it would work when deployed (or sent to a User, in this case), notice on the right hand side, you get a way to deploy the Card whether in a Chat as a link or through a Flow.

    In this example, I’ll choose a Flow.

  8. Now, it’ll initialize a Flow template with necessary steps.

  9. When ready, it’ll give this template for me to complete the Flow.


    Now, in the next section, let’s continue to finish the Flow and send it to an actual user. (Myself 😊)

Sending a Power Apps Card to Teams Chat

Now, let’s work on our Flow to be ready to run –

  1. First step is to Initialize the Card itself with an instance of the Card. Here, we’ll select the Card we just created.

  2. In the second step, you can actually choose who should the Card go out as.

  3. Then, it as ask what should should it post into. I’ve selected Chat with Power Apps since I wanted it to as a personal chat.

  4. Finally, it also needs a recipient – I’ve selected myself here to test it out.

  5. Now, when I run the Flow, I receive a chat message from Power Apps like below –

  6. And it then runs the Card itself! When I click the button as configured, it’ll read the user and display the name.



    Here’s the result!

Hope this was useful!

Thank you!

Button to send Email based on Templates in Dynamics 365 CE

Great blog below by Vidit to demonstrate how you can use ribbon buttons in Dynamics 365 Sales to send emails based on Templates.

Power Platform Pipelines | Blog Series

Here’s a blog series to get you up to speed on Power Platform Pipelines!

Setting up and Running Power Platform Pipelines

Here is what you need to get done in order to setup Power Platform Pipelines –

  1. Setup Power Platform Pipelines
  2. Run a Power Platform Pipeline

Advanced Settings

ScenarioBlog
Once request for deployment is submitted.Pre-Export Step Required setting in Deployment Pipeline | Power Platform Pipelines

Here’s official Microsoft Documentation on Power Platform Pipelines – https://learn.microsoft.com/en-us/power-platform/alm/pipelines?WT.mc_id=DX-MVP-5003911

Hope this was useful!

Thank you!

Enable Copilot for Dynamics 365 Sales environment

Copilot for Dynamics 365 Sales is in Preview at the point of writing this post. Hence, I’ll start by showing how you can turn Copilot for Dynamics 365 Sales on for your environment.

It is recommended to do this in your Sandbox instances first.

Enable Copilot for Dynamics 365 Sales

Given that you have the correct licenses setup and you are a System Administrator, you can follow the below steps in order to enable Copilot for Dynamics 365 Sales –

  1. Make sure you are in the Sales Hub app.

  2. And then go to the App Settings

  3. Here, you’ll see the Copilot as an option on the Sitemap, select that.

  4. Note that all the Settings are turned off by default.

  5. First thing you can do is, turn Auditing On. It’ll take a while to Save the changes in the background.

  6. Then, you can turn on other features which are in Preview On and enable the Copilot App based on your Published apps in your environment.

  7. Here are the Preview features which are listed under the See what’s in preview link in the above screenshot – https://learn.microsoft.com/en-gb/dynamics365/sales/view-copy-email-summary
  8. Once the changes are saved, it’ll look like this in the Published state. the selections will remain the Publish button will be disabled.

  9. At this stage, the Copilot has been enabled for the selected Apps in your environment.
    Now, you can move to other options like Opportunities and Leads tabs on the settings page.
    The Summary section in the entities will show which fields should be included in Summary information that Copilot will generate.
    The Recent Changes in the entities will show which fields should be included to keep track of the changes which happen on these fields.


At this point, you are all set in configuring Copilot in your Dynamics 365 Sales environment. Next, I’ll write about how we can use the features which we enabled in this post and I’ll share link of the upcoming post here.

Hope this helps!

Thank you!

Enable Copilot for Project Operations

Recently, you must have observed Copilot being introduced in every other Microsoft Business and M365 applications. Dynamics 365 Project Operations too being no exception! Here’s how you can get the same

Enable Copilot in Project Operations

Here’s how you can enable Copilot in Project Operations –

  1. In Project Operations app, Navigate to Settings in the SiteMap area –


  2. Then, Navigate to Parameters. Then, open the Parameter record itself (Avoid click on the Default Organization Unit as it’ll take you to the Org Unit record and not the intended Parameter record).

  3. Then, you can drop down from the Feature control and see that the Copilot option is available to enable for you.

  4. Once you click on it, it’ll ask you for confirmation. Click OK if everything looks good to you.


    It takes a few moments for Copilot to be enabled for Project Operations environment.

Disable Copilot

Here’s how you can disable Copilot if not needed –

  1. In case you don’t want to use Copilot and want to disable it, you can open the Parameter record in Project Operations’ Settings area and drop down from the Feature Control ribbon button to find that you can now Disable Copilot if it is in enabled state.

Hope this post was useful!

Thank you!

Starting a Project Operations Lite Trial Environment

One of the first things you want to get done is to spin up a Project Operations Trial environment. Here’s how you do it!
Note that no Credit Card is required for a Project Operations trial environment.

Project Operations Trial Environment

Here’s how you start a Project Operations trial environment –

  1. Navigate to https://trials.dynamics.com/ which will be redirected to https://dynamics.microsoft.com/en-us/dynamics-365-free-trial/ and the page you’ll see will be something like this –

  2. Scroll down on the page till you see the option for Project Operations. Click on Try for free.

  3. Once you click on Try for free, you can enter a new email on which you want to start a trial. I’ve come up with a sample email which I haven’t used before. I prefer not to enter an email/username which I already use.

  4. Click Next and then you can select Setup my account.

  5. Then, you can validate/enter the details which would be something like this and click Next.

  6. Then, choose if you want to receive an OTP via Text or a Call. Text is my preferred way so I selected that and clicked on Send verification code.

  7. I received an OTP which I entered as asked on the next pane and clicked Verify.

  8. Further, I’ll be shown the login details of the trial environment I want to create. Once this is done and I save the information, I click on Next.

  9. Then, you’ll be shown the details of the environment you’ll be provisioning. Save this info before proceeding.
    Next, click on Start using Dynamics 365 Project Operations (CE) – Preview Trial. It’ll redirect you to the questionnaire page on a new tab where you’ll need to answer the questions before choosing the Deployment Type.

Deployment Type Questionnaire

As we left off from the Step #9 in the above section, you’ll be taken to a questionnaire Wizard in order to provision a Project Operations trial –

  1. Yes to managing Opportunities as they move through the process.

  2. Yes to requiring advance or extensible resource management.

  3. Yes to requirement of workflow for approval of Time and Expense.

  4. No to advanced Expense management.

  5. No to Non-Stocked Materials

  6. No to Stocked materials as well.

  7. Select the version here. Even if you would have answered the questions randomly, you would have still gotten to choose a different version than recommended. Hence, the answers above point to a recommendation of Project Operations Lite type of Deployment.
    Click Begin Setup once Lite Deployment is selected.

  8. Setup will start provisioning once you click on Start.

  9. And it’ll take a while and it’ll say that it will redirect you to the Power Platform Admin Center.

  10. And once you are redirected to Power Platform Admin Center and you’ll see that the environment is provisioning. This will take a few minutes before completion.

Set Name and URL for your environment

Provisioning a Project Operations trial will get set a predefined URL and name which you should update to be readable –

  1. Open the environment once the link is clickable and the State is set to Ready.
  2. Then, click on the Edit button

  3. Once you click Edit, you’ll get to update the Name and the URL. Set to something that is relevant to the purpose of the environment.

  4. Once you click on Save, you’ll see this loading page which will take a while to complete and finally, your Project Operations Lite environment setup will be ready!

Here’s Microsoft’s Documentation detailing which all Deployment Types have different Project Operations features available – https://learn.microsoft.com/en-us/dynamics365/project-operations/environment/determine-deployment-type?WT.mc_id=DX-MVP-5003911

Hope this post was useful!

Here are some Power Automate posts you want to check out –

  1. Select the item based on a key value using Filter Array in Power Automate
  2. Select values from an array using Select action in a Power Automate Flow
  3. Blocking Attachment Extensions in Dynamics 365 CRM
  4. Upgrade Dataverse for Teams Environment to Dataverse Environment
  5. Showing Sandbox or Non Production Apps in Power App mobile app
  6. Create a Power Apps Per User Plan Trial | Dataverse environment
  7. Install On-Premise Gateway from Power Automate or Power Apps | Power Platform
  8. Co-presence in Power Automate | Multiple users working on a Flow
  9. Search Rows (preview) Action in Dataverse connector in a Flow | Power Automate
  10. Suppress Workflow Header Information while sending back HTTP Response in a Flow | Power Automate
  11. Call a Flow from Canvas Power App and get back response | Power Platform
  12. FetchXML Aggregation in a Flow using CDS (Current Environment) connector | Power Automate
  13. Parsing Outputs of a List Rows action using Parse JSON in a Flow | Common Data Service (CE) connector
  14. Asynchronous HTTP Response from a Flow | Power Automate
  15. Validate JSON Schema for HTTP Request trigger in a Flow and send Response | Power Automate
  16. Converting JSON to XML and XML to JSON in a Flow | Power Automate