Setup D365 Sales with Dual-Write to Finance and Operations – Part 2

And let’s get to the Solution setup part!

In Part 1, we created a Dynamics 365 Sales environment and added Finance and Operations to it – all from the Power Platform Admin Center. Now, let’s set up Dual-Write so your Accounts flow to Finance and Operations as Customers.

Here’s how I set it up –

1. Setup Dual-Write

  1. Back in Power Platform Admin Center, open the environment, go to Resources > Dynamics 365 apps and click Install app. Install the Dual-write packages one at a time, waiting for each to show Installed: first Dual-write core solution, then Dual-write Application Core Solutions (legal entities, currencies), and then Dual Write Finance and Extended Solutions – this one has the Customers V3 map we need for Accounts.
    Dual-write core solution, Application Core Solutions and Finance and Extended Solutions installed - the orchestration solution failed
    Note: I first tried the all-in-one Dual-write application orchestration solution, but it failed with Cab file required for importing solution with name Dynamics365FinanceAndOperationsAnchor, even after a retry. Microsoft now ships these as separate packages – so install those instead.
    Error details for the Dual-write application orchestration solution: Cab file required for importing solution Dynamics365FinanceAndOperationsAnchor
    Tip: Don’t start the next package until the previous one shows Installed – each one builds on the one before, and running them in parallel in the same environment can make the installs fail. For me, the Dual-write core solution took about 20 minutes, so plan for some waiting time here.
  2. Now open Finance and Operations and go to Workspaces > Data management and click the Dual-write tile. Since Sales and Finance and Operations are in the same environment, it’s already linked – no linking wizard like the old Lifecycle Services days.
    Dual-write tile in the Data management workspace in Finance and Operations
  3. Before applying any maps, check which legal entities are linked. Click Environment details > Legal entities. In my case, only dat was linked, but the Contoso demo data lives in USMF. So click Add Legal Entity, select USMF and Save. Keep Skip initial writes for newly added legal entities checked if you only want new records to sync.
    Adding the USMF legal entity to the Dual-write link
  4. Click Apply solution, select Dual-write application core entity maps and click Apply. Once it’s applied, you’ll see the table maps listed with a status of Not running.


    Troubleshooting: In my environment, Apply solution came up empty with the error Failed to get solutions containing entity maps … StatusCode=NotFound, and Add table map failed with Failed to get publishers available to user. Here’s what I checked:
    – I ran Health check on the Dual-write page – all 15 checks passed (core solution, orchestration components, app users, plugins, API Hub connection and business unit).
    – Since this was a unified environment where the Dual-write link was created automatically during provisioning, I used Reset link to recreate the connection under my own account – choosing the current Dataverse environment and the dat and USMF legal entities. The reset completed successfully (15/15 checks passed).
    Reset link to Dataverse summary with dat and USMF legal entities and 15 of 15 checks passed
    – Even after the reset, Apply solution returned the same NotFound error – which points to the Dual-write service side rather than the setup. If you hit the same error, raise a support ticket with Microsoft and include the Session ID and Root Activity ID from the error. I’ll update this post once it’s resolved.

So what’s actually going wrong?

At this point everything looks healthy – all three Dual-write packages are installed, the link shows both legal entities, and the Health check passes 15/15 – but Apply solution still returns Failed to get solutions containing entity maps … StatusCode=NotFound. So what gives?

“Apply solution” doesn’t read those entity maps from your environment – it calls a Dual-write backend service that returns the list of solution maps for your two linked environments. A NotFound from that service means the call reached it but it had nothing to hand back – the environment pair isn’t registered on the service side yet, even though the solutions are physically installed in Dataverse.

In my experience this comes down to one of a few things, and it’s worth checking them in this order:

  1. The link was created by provisioning, not by you. On a unified environment, the Sales + Finance and Operations link is set up automatically. The account that created it owns it, and other admins can get NotFound / “Failed to get publishers available to user” until they re-create it. Reset link (which I did above) is meant to fix this – it did put the link under my account, but the service still returned NotFound, so for me it wasn’t the whole story.
  2. The environment pair is still catching up on the service side. A freshly provisioned Finance and Operations environment (mine finished only hours earlier) can take a while before the Dual-write service recognises the pair. A NotFound that persists right after setup, then clears on its own, usually points here.
  3. App registrations / dual-write app users. The Health check lists the two app users and app IDs that let Dataverse and Finance and Operations call each other. If one of those is missing or not consented at the tenant level, the backend call can’t authenticate and returns NotFound rather than a clear auth error.

Since the Health check passed and the Reset didn’t clear it, my case looks like a service-side registration delay (reason 2). The fix there is time plus a Microsoft support ticket with the Session ID and Root Activity ID from the error. I’ll update this post with the map and test steps once Apply solution returns the solutions.

Hope this was helpful!

Here are some more posts you want to check out –

  1. Deploying Project Operations Core vs Integrated with ERP
  2. Environment Groups in Power Platform Admin Center
  3. Preferred Solution in Dataverse | Power Platform Admin Center
  4. Enable Copilot for Dynamics 365 Sales environment

And some popular Power Automate posts –

  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. Call a Flow from Canvas Power App and get back response | Power Platform
  4. Asynchronous HTTP Response from a Flow | Power Automate

Thank you!

Setup D365 Sales with Dual-Write to Finance and Operations – Part 1

While Setting up Dual-Write with Project Operations is a no-brainer, often times – setting this up with other applications like D365 Sales needs to take a different route.

If you are using Dynamics 365 Sales and want your Accounts, Contacts and Products to flow to Finance and Operations, Dual-Write is the way to do it. And with the new Power Platform Admin Center experience, you don’t need Lifecycle Services anymore – everything starts from PPAC.

Here’s how I set it up end to end –

1. Create the Sales Environment

  1. In Power Platform Admin Center, go to Manage > Environments and click on + New. Give it a Name, select the Type as Sandbox and the Region – I’ve selected United States here. Then, expand Change default settings, set Add a Dataverse data store? to Yes and click Next.
    New environment pane in Power Platform Admin Center with Dataverse data store set to Yes
  2. On the Add Dataverse pane, select the Currency (I’ve chosen USD), Security group as None (since this is a sandbox for demos) and enter a URL of your choice. I’ve given it the same name as the environment. Keep the URL short – the Finance and Operations Provisioning App needs it to be 19 characters or less.
    Add Dataverse pane with USD currency, no security group and custom URL
  3. Now, set Enable Dynamics 365 apps? to Yes and in Automatically deploy these apps, select Sales Enterprise.
    Enable Dynamics 365 apps set to Yes with Sales Enterprise selected
  4. Note: Don’t try to select Sales Enterprise and Finance together here – PPAC doesn’t allow it, you’ll get an error saying the app ‘Finance’ cannot be provisioned with other apps. We’ll add Finance and Operations once Sales is ready.
  5. Click Save and the environment will start Preparing.
    D365 Sales with DW environment in Preparing state

2. Add Finance and Operations to the Sales Environment

Once the Sales environment is Ready, we’ll add Finance and Operations to the same environment. You’ll need to install the Finance and Operations Platform Tools first, and then the Finance and Operations Provisioning App. I’ve covered these steps in detail in this post – Deploying Project Operations Core vs Integrated with ERP.

  1. First, make sure your Sales environment shows as Ready.
    D365 Sales with DW environment in Ready state
  2. Open the environment, go to Resources > Dynamics 365 apps and click Install app. Select Dynamics 365 Finance and Operations Platform Tools and click Next. You may see this app listed more than once – any of them works.
    Dynamics 365 Finance and Operations Platform Tools selected in the install list
  3. Agree to the terms and click Install. You’ll see a banner that the installation has started.
    Finance and Operations Platform Tools installation started banner
  4. Once Platform Tools shows Installed, click Install app again and select Dynamics 365 Finance and Operations Provisioning App (again, you may see it listed more than once). Click Next and confirm – this opens the Provisioning App setup in a new tab.
    Finance and Operations Provisioning App selected in the install list
  5. On Settings, I’ve ticked Enable Demo Data for Finance and Operations – this gives us sample customers and products to test Dual-Write with. Leave Developer Tools unchecked unless you need them.
  6. On Version, select the latest version available to you and click Next.
  7. Review, agree to the terms and click Install. As the screen says, this can take a couple of hours but Dataverse (and your Sales app) stays available during the installation.
  8. Once the installation completes, the environment page shows a Finance and Operations URL next to the Environment URL. Click it to open Finance and Operations – same environment, same Dataverse as your Sales app.
    D365 Sales with DW environment showing the Finance and Operations URL and details

That’s the environment ready with both Sales and Finance and Operations. In Part 2, we’ll set up Dual-Write and see Accounts from Sales flow into Finance and Operations as Customers.

Hope this was helpful!

Here are some more posts you want to check out –

  1. Deploying Project Operations Core vs Integrated with ERP
  2. Environment Groups in Power Platform Admin Center
  3. Preferred Solution in Dataverse | Power Platform Admin Center
  4. Enable Copilot for Dynamics 365 Sales environment

And some popular Power Automate posts –

  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. Call a Flow from Canvas Power App and get back response | Power Platform
  4. Asynchronous HTTP Response from a Flow | Power Automate

Thank you!

New Project Team Experience (OneGrid) in Project Operations

If you’ve been using the Team tab on a Project in Project Operations, there’s a new experience you can switch on now – the Team Member grid can use the Power Apps OneGrid control, the same modern grid you are already seeing across other areas of the app.

Here’s how to enable it and what changes on the Team tab – before and after –

Enable the Feature

  1. In Project Operations, change the area to Settings and open Parameters. Open the Parameter record and drop down Feature Control. Look for Enable OneGrid for Team Member – notice it doesn’t have a check mark yet.
    Enable OneGrid for Team Member highlighted in the Feature Control menu
  2. You’ll be asked to confirm. As the message says, the Power Apps OneGrid control will now be used for the Team Member grid on the Project form. Click Enable. Note: once enabled, the option no longer appears in the Feature Control list, so do this on a Sandbox first and see how your users like it.
    Enable button highlighted on the OneGrid confirmation dialog

Before

  1. Here’s how the Team tab looked on my project before enabling the feature – a regular subgrid with + New, Refresh and Flow.
    Team tab on a project before enabling OneGrid
  2. And when I expand a team member, I see the tasks they are assigned to. Selecting the row gives me Generate Requirement and Subcontracting Options.
    Expanded team member showing task assignments before enabling OneGrid

After

  1. Now, on the same project, the Team tab uses the new grid. You get checkboxes to select rows, the Bookable Resource, Role, Resourcing Unit and Position are now clickable links, and there’s a new Add Existing Project Team button right next to + New. At the bottom, you also get a Rows count.
    Team tab on the same project after enabling OneGrid
  2. Expanding a team member now opens a proper nested grid for the task assignments – with its own checkboxes, links to the Task, Bookable Resource and Role, an icon to open each assignment record and a Rows count of its own. When I select the team member, Generate Requirement and Subcontracting Options are still right there, and the footer shows how many rows are selected.
    Expanded team member showing the nested assignments grid after enabling OneGrid

So nothing changes in how you staff your project – it’s the same actions, just in a grid that’s easier to work with, especially on projects with larger teams.

Hope this was helpful!

Here are some more Project Operations posts you want to check out –

  1. Deploying Project Operations Core vs Integrated with ERP
  2. Hide Resources from Schedule Board in Project Operations [Quick Tip]
  3. Resource Roles and adding Role Prices to Cost and Sales Price List in Project Operations
  4. Permissions in Project in Project Operations
  5. New Copy Project Experience in Project Operations
  6. Project Task Progress Update in Project Operations & Mark Task as Completed

And some popular Power Automate posts –

  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. Call a Flow from Canvas Power App and get back response | Power Platform
  4. Parsing Outputs of a List Rows action using Parse JSON in a Flow
  5. Asynchronous HTTP Response from a Flow | Power Automate
  6. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Deploying Project Operations Core vs Integrated with ERP

So what was known as “Project Operations Lite“, “Project Operations Non-Stocked/Resource” and “Project Operations Stocked/Production” type of deployments are now – Core, Integrated with ERP and Manufacturing. In this post, we’ll focus on Core and Integrated with ERP.

And with LCS sunsetting, this is even easier with just the Power Platform Admin Center. Let’s see how!
But first, a quick look at the differences between them –

Which Deployment Type do you need?

CoreIntegrated with ERP
Old NameLiteResource / non-stocked
App LayersDataverseDataverse + Finance (dual-write)
Distinguishing FeaturesProforma invoicing, URS, Project for the webCustomer invoicing, revenue recognition, full expense with receipt OCR
PPAC App SelectionProject OperationsProject Operations ERP

If you are unsure what applies to your use case, it helps to take this questionnaire to get to what Microsoft suggests – https://admin.powerplatform.microsoft.com/projectoperations

1. Deploy Project Operations Core

Deploying Project Operations Core is fairly simple, just like deploying any other Dynamics 365 App. Let’s breeze through this quickly –

  1. Given you have access and the right privileges in the Power Platform Admin Center, create a new Environment.
    Give your environment a suitable name and then make sure to enable the Data Store, meaning Dataverse will also be deployed with the environment.
    New environment with Dataverse data store enabled in Power Platform Admin Center
  2. Then, make sure the correct Currency and Security Group are selected as they are required.
    Then, select Enable Dynamics 365 Apps? as this will help you choose which Apps to deploy for your Environment.
    Enable Dynamics 365 apps option in Power Platform Admin Center
  3. Then, select only Project Operations. This is the Core type amongst the others and will be deployed as CE only, without any integration to ERP/F&O.
    Project Operations app selected for a Core deployment
    Click Save and let the environment get provisioned for a while. This will be relatively quicker than the other Project Operations deployment type.

2. Deploy Project Operations Integrated with ERP

So, you already have the right Power Platform Admin privileges. Here are the steps to create both the Project Operations environment and a new F&O environment, and tie them together –

  1. Start by creating a New environment and enter the right region and name of the environment. Make sure to select Add a Data Store before you move to the next page.
    New environment with region, name and Dataverse data store
  2. Then, give it an appropriate URL. Note that this is also what the URL of the F&O environment will end up being.
    Then, select Enable D365 Apps and in the list, select the Project Operations ERP app.
    Enable Dynamics 365 apps set to Yes
    Project Operations ERP app selected
    And once you click Save, it’ll start Provisioning as below –
    Environment in Preparing state
  3. Once it’s deployed, you’ll find that you also get the F&O link in it –
    Project Operations environment with the Finance and Operations URL

But what if you already have an environment with Project Operations only and want to set up F&O with it?

  1. Already have an environment? Install the Finance and Operations Provisioning App on it instead of creating a new one. But first, you’ll need to install the Finance and Operations Platform Tools. Here’s how you go about it –
    In your Project Operations environment, drop down Resources and select Dynamics 365 Apps.
    Resources menu with Dynamics 365 apps
  2. Then, click Install app.
    Install app button on Dynamics 365 apps
  3. Then, look for Finance and Operations Platform Tools and click Next.
    Finance and Operations Platform Tools app
  4. Confirm the details you see – the Finance and Operations Package Manager will get installed.
    Confirm Finance and Operations Package Manager installation
  5. Once this is installed, install the Finance and Operations Provisioning App.
    Finance and Operations Provisioning App
  6. Confirm when asked – this opens up in a new tab. Select the options and proceed.
    Provisioning App options
  7. Then, select the latest version available to you when you set this up [it could vary when you are reading this] and click Next.
    Select the Finance and Operations version
  8. Confirm that the options you selected appear checked.
    Agree and install
  9. It’ll install for a while and once ready, the Finance and Operations URL will appear on your Project Operations environment.
    Finance and Operations URL on the environment

Hope this was helpful!

Here are some more Project Operations posts you want to check out –

  1. Difference between Project Operations Deployment Types
  2. Starting a Project Operations Lite Trial Environment
  3. Setting up Project Operations Lite | Blog Series
  4. New Copy Project Experience in Project Operations
  5. Permissions in Project in Project Operations
  6. Environment Groups in Power Platform Admin Center

And some popular Power Automate posts –

  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. Call a Flow from Canvas Power App and get back response | Power Platform
  4. Parsing Outputs of a List Rows action using Parse JSON in a Flow
  5. Asynchronous HTTP Response from a Flow | Power Automate
  6. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Work with your Dynamics 365 CE data from Copilot using Dataverse MCP

If you are already using Copilot via an M365 Copilot license and it is helping you in productivity already – you might want to take it a step further and enable it to also bring in your Dynamics 365 CE data together – be in Project Operations, Field Service, Sales, Customer Service etc.

Examples: Copilot is helping me with my emails, SharePoint files – summarizing and triaging information. But have to still log into Dynamics 365 to get work done. Well, by default this is not enabled for organizations and ready to use but your Admin team can help you enable this.
Make sure the users who will use this have an M365 Copilot license assigned to them and you have the right Admin privileges across M365, Power Platform Admin Center, Azure and Teams Development Portal.

Let’s see it how and make it work!

Step 1 – Register an App in Microsoft Entra

Give you have the right access to Azure with permissions, you need to create a new App Registration and follow the steps along –

  1. Add a new App Registration in Azure Portal.

  2. Then, enter the Name and select Web in the Redirect URI [https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect]

  3. Once the App is registered. Save the App Registration ID and Tenant ID.
  4. Then, navigate to the Certificates & secrets. And add a new Client Secret there.


  5. Now, store the value before you refresh the page. You’ll need the Secret Value.
  6. Now, go to API Permissions as below.

  7. Select Dynamics 365 CRM and mcp.tools as Delegated access.
    Then, grant the permissions.





    And finally, Grant the permissions as below.


    And check that the Permission is granted.

Step 2 – Allow the App on the Dataverse MCP Server using Power Platform Admin Center

  1. Given you have Dynamics 365 Admin privileges, navigate to Power Platform Admin Center. Navigate to your environment and look for Features under Settings.


  2. Then, navigate to Data Model Context Protocol and make sure Allow MCP clients to interact with Dataverse MCP server (GA version) is enabled. [Based on when you are reading this blog, the mention of version might change]

    Click on Advanced Settings which will take you in Dynamics CE to.

  3. Click on new MCP Client.

  4. You already have the Application ID from Azure’s App Registration. Copy it as you’ll need it here.
    Then, enter register the App Registration as an MCP Client here. Give it a suitable name, but also make sure to add prefix yourself. I just added “new_”
    Set Is Enabled to Yes. Save the record.


    This is set now.

Step 3 – Register the OAuth Connection in Teams Developer Portal

You need to register the OAuth Endpoint here.

  1. Navigate to Tools as shown and then select OAuth Registration.

  2. Register a new client. This will be similar to App Registrations you’ve used to doing before. Just that the information is to be borrowed from the App Registration on Azure we did above.
    Click Register client.
  3. Fill in the details as asked

  4. Once created, copy the Reg ID. You’ll need this in the Reference ID asked in the Microsoft Copilot Portal below.


    Here, you are now ready to consume this to create a new Custom Connector in M365 Admin Center’s Copilot area. Let’s see ahead.

Step 3 – Create the Connector in Microsoft 365 Admin Center

Given that you are an M365 Global Administrator, you need to now deploy this as a Custom Connector in M365 Admin Center under Copilot –

  1. Go to M365 Admin Center [https://admin.cloud.microsoft/]. Then, expand Copilot on the left hand pane and look for Connectors.

  2. Register your Connector. Enter the name and the info like the URL, and Description which are mandatory.

  3. Further, add more details as asked and the copied Reference ID from Teams Developer Portal app is to be pasted here. Refer Step 3 and point #3 from above.
    Now, click Authorize.

  4. Then, click Authorize again. It should go through and show as below. Then click, Create at the bottom.


    Once created, it’ll be available like this.


    Now, let’s roll it out to the users!

Step 5 – Roll it out to your Users

Now, let’s roll it out to the users. Follow the steps below –

  1. Navigate to the Copilot area in the the left hand pane. Look for Connectors, under Your Connections, wait for a bit for the list to refresh. You’ll find yours there. Click on the three dots and then click Add Staging.

    It takes a few mins for this to be available to the selected users.

Step 6 – Connect from Copilot Chat

Now, let’s test!

  1. In your Copilot Chat, look for the gear icon next to your profile, then navigate to Settings.

  2. Look for Sources, you’ll see list of Connectors available.


  3. Search for your Connector there and it’ll show up. Once you find it, click Connect on the Connector. It’ll authenticate you in.

  4. Click Continue and you should be connected in a moment.

  5. Then, you can also look at what tools are available for you to use.

    And you are all set. Let’s test.

Query your CRM data here!

Now, you can start by querying your CRM data here – just ask anything from the environment and validate if it is returning correct answers. Involve System Admins and the ones who deployed if you need to further fine tune your Connector.

Hope this was helpful!

Here are some more Dataverse and Copilot posts you want to check out –

  1. Code Apps for Dataverse – Part 1
  2. Code Apps for Dataverse – Part 2
  3. Finding Indexed Columns in Dataverse Search
  4. Time and Expense Agent [Production Ready Preview] – Part 1
  5. Enable Copilot for Dynamics 365 Sales environment
  6. Create Project Plan using Copilot in Project Operations
  7. Environment Groups in Power Platform Admin Center

And some popular Power Automate posts –

  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. Call a Flow from Canvas Power App and get back response | Power Platform
  4. Parsing Outputs of a List Rows action using Parse JSON in a Flow
  5. Asynchronous HTTP Response from a Flow | Power Automate
  6. Converting JSON to XML and XML to JSON in a Flow | Power Automate

Thank you!

Code Apps using Claude Code – Power Platform

As straight forward as the title is deploying Code Apps from the start. If you are in Power Platform already, here’s where the evolution is from –

  1. Model-Driven Apps [Traditional Power Platform / Dynamics 365 CRM forms and View, Sitemaps and all of that you’ve known so far]
  2. Canvas Apps – Close to a decade to blend the experience of Power Point but to build Apps that connect to data sources and design things the way you like.
  3. Code Apps – [Build Practically Anything, sits in Power Platform]

I have a 2-blog series to explain Code Apps and I’ll continue to enrich this blog as a placeholder for Code Apps and making it easy for you to follow through and get your first one out even if you feel you are too late –

  1. Code Apps for Dataverse – Part 1 [Using VS Code and Claude Code] – Getting Started
  2. Code Apps for Dataverse – Part 2 [Updating your Apps and Deployment]

    And also check Power Platform experience to Vibe-Code your Code Apps without really leaving the Power Platform experience at all – Power Apps Vibe Coded Experience [Preview]

Hope this was helpful!

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

Thank you

Advances and Retainers in Project Operations

Below is how you can setup Advanced and Retainers – and what is this in simple terms?

  1. Pre-Bill the Customer upfront.
  2. Reconcile the Billing amount before the next Billing cycle.
  3. If under-utilized or till the Amount, 0 is billed on.
  4. If over-utilized, the overage is billed to the customer on the Invoice created on Contract.

Setup Contract for Retainer Schedule

On the Contract for a combination of T&M and Fixed Price Contract Line, here’s how I setup the Retainer Schedule –

  1. Here are the Line Items on the Project Contract tied to the same project.

  2. And on the Contract, you have Advanced and Retainers Setup already.

  3. Here, you have the option to Setup the schedule.


  4. When you click on Setup a retainer schedule, it’ll ask you to fill out the details. You can either select and End Date for the Retainer of no. of Retainer Invoices to be created.
    But, the message isn’t shown till you realize it after you enter both.


    And when I tried to enter this – it gave me an error.

  5. So, I just kept the End Date

  6. And it’ll create the Schedule for me.

    Now, this is set.

Invoice the Retainers

Now, the Retainer Schedule is ready, let’s Invoice and confirm the Invoice –

  1. I can select the Retainer line and click on Ready to Invoice.

  2. Once this is ready, I can create the Invoice from the Contract.

  3. Once the Invoice is created, you’ll see that the Advances and Retainers section shows the Invoiced line item.
    Now, you confirm this Invoice.


  4. Once the Invoice is confirmed, this amount is available to be used on the Contract.


Consuming the Retainers

Now, this amount is available for us to consume on the Project. Let’s pre-date the Time Entries to see how the Available Amount is consumed –

  1. These are my time entries. And I’ll submit them.

  2. The Project Approver approves them so that Actuals are created which can be made as Ready to Invoice.


    Now, the Unbilled Sales will be made as Ready to Invoice.

  3. Now, as usual – Invoice will be created without doing anything to the Contract Retainer setup.

  4. Now, the Pro-forma Invoice will be created and the Amount is seen on the Line Items of what was Ready to Invoice but the Invoice amount itself will be 0.

  5. If you scroll to the bottom of the Invoice, you’ll see the Balance remaining due to this Invoice.

  6. Now, you confirm the Invoice.

  7. And once the Invoice is Confirmed, the Used Amount on the Contract’s Retainer schedule will be updated.


    If you over use the balance, the upcoming Invoice will have less amount to be billed based on what’s available.

Hope this was helpful!

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

Thank you

Code Apps for Dataverse – Part 2 [Updating your Apps and Deployment]

Now that we learnt how to get started and put up your first blank app in Code Apps for Dataverse – Part 1 [Using VS Code and Claude Code] – Getting Started. In this post, we ‘ll understand how you can continue to work with your Code Apps like you would for any other solutions in Dataverse.

Pushing your App to the Environment

Now that Code Apps was run locally and hosted on the environment. We’ll see how it is coming along –

  1. Code Apps was running on Localhost as we saw in the previous post. You can always use the command pa app run to test this and it’ll give you a URL which on the browser of your environment will appear like this –


  2. Now, you can check if this is published or not by running pa app list


  3. And then, you’ll be able to push this to the environment itself.
    First, npm run build and then pa app push
    This will first build the app locally and then push it to the environment.


  4. Here, the App is now pushed to your preferred Solution which you have set for your evironment.

    Now, the App is on the environment and can be run from there.

Update Your Changes

Now that the App is deployed, I’ll continue to make more changes to it –

  1. Just chat with Claude Code and build your App first. Like so –

  2. Once all the changes are written – you can run pa app run to run the App server locally.


  3. Now, once you copy the URL it gave back – basically the same one which is generated for localhost.
    It’ll now show the changes you did.



  4. And then again, push the changes to the environment. Using the same commands –
    npm run build
    pa app push

Running the App on the Environment

We have not run it locally, let’s run it on the environment –

  1. Locate your App like you would do for any Canvas/Model-Driven app and you can simply Run it.

  2. But here, something is wrong – it didn’t load my app. Maybe something is missing and I need to debug. Correct?

    This segways into debugging mode.

Debug the App on the Environment

Now, let’s debug the App on the environment –

  1. Simply chat with Claude Code explaning the issue. Follow the instructions based on what it says and every time the App is updated, run npm run build and then pa app push to keep pushing your changes to the environment and keep checking.

And that’s pretty much how you go about it.

Hope this was helpful!

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

Thank you

Code Apps for Dataverse – Part 1 [Using VS Code and Claude Code] – Getting Started

Code Apps has been our earlier this year and I’ve seen people start to use it already. But some stumble upon it and somehow end up creating and managing it – but when we try to remember where we started, it get a little blurry.

Also, this is great segway to move to something not Microsoft-native from a development standpoint and moving away from using Visual Studio (traditionally for C# .NET Framework Plugins) to Node.js based vibe-coded Code-App development.
So, we’ve come from Model-driven Apps -> Canvas Power Apps -> now Code Apps!

Let’s get your first Code Apps out of th door.

Enable Code Apps in your Power Platform Environment

Given you might be a Power Platform / Dynamics 365 Admin already, go to the your Environment’s Settings as below –

  1. Look for Features –

  2. Then, Code Apps might already be Disabled, you need to Enable it.

  3. Make sure to Save the settings and check if it is enabled.


    That’s it, you’re set. Now let’s get your environment setup.

Setup your VS Code with with Node.js [and Claude Code] to start writing your Code App

Suppose you are using VS Code [the most popular choice for coding lately 😊, or vibe-coding with Claude Code], here’s how you set it up –

  1. Make sure Node.js is setup on your machine post. Check it using Claude Code on Visual Studio.
    Use “node –version” to check the installation is in place.


    In case Node.js is not installed – on a Mac, use Homebrew to get it or from winget on a Windows machine.


  2. That set up, now – Power Apps CLI or “pac cli” for short.
    So, check using pac –version
    I’ll ignore the rest of the message for now.


  3. Now, my preference is to build locally and then host it on the environment. So, my next step is – to authenticate Power Platform CLI to the target environment.


    One of the ways to authenticate Power Apps CLI is to also use Device Login method. In that case, use the below –


  4. Use pac org who to confirm if you are authenticated into the correct environment.


    Here, you are set with your tools. Now, let’s create a project locally.

Setup A Local App Folder

Now, let’s setup a local app folder now that your tools are authenticated and ready.

  1. Run the command to create a Project folder locally and name your app.

  2. Now, once I run this in Terminal on my VS Code, it’ll create the App.


  3. As this looks good, I’ll now go ahead and initialize this in my connected environment.
    Using this command pa app init --display-name "Project Profitability Dashboard" --environment-id XXXXXX-XXXX-e9d2-8c94-e577a72007d7
    Once you run it in your terminal, it’ll give you this on your browser

  4. Confirm the local build using ls command.

    You’ll see the files listed. Now you are all set.

Add Data Source to the Code App

Now, let’s add Data Source to the code App. In this case, it’ll be our Dataverse environment itself –

  1. Use this command pa app add data-source shared_commondataserviceforapps to add the Data source. I’m not using a Connection Reference so it just took my Entra ID.


  2. And I select the connector, it’ll be finally connected. Now, since this is a blank project, just add a dev script using npm install --save-dev vite

  3. It’ll create the same code and you are done. Now, you can continue to talk to Claude Code to build your Code App and run it using pa app run


    Now, we’ll see how the App can run and your changes can start panning out!
    Part 2 – Code Apps for Dataverse – Part 2 [Updating your Apps and Deployment]

Hope this was helpful!

Thank you

AI in Dynamics 365 CE Applications: Transforming Solution Architecting

Given my 12.5 years in the industry at this point – where I started my journey from Dynamics CRM 2013 online (and having dealt with some D365 CRM 4.0 on-prem along the way too) – I’ve come a long way from changing XML for SiteMaps to make sure the Calendar is set right for new orgs – features in D365 CRM got added and many features kept getting deprecated [Although the later is less than the former].

The only help I get and also which I offered was treacherous hours and hours spent in making sure the. ‘customer experience’ is top notch as much as the quality of my solutioning.
Now, sitting in later half of 2026 and putting even the Solution Architecting years behind me – I look back in time and gauge what has changed really?

Well, fundamentally things remain the same –

  1. Set up new environments
  2. Implement C# plugins and JS for custom logic
  3. Configure roles, System Settings
  4. Configure behind the scenes for applications like Project Operations, Field Service, Customer Service etc.
  5. Migrate and deploy solutions between environments

    …and so on.

But, the medium of doing all the above has changed. That definitely has!

With advent of AI tools – Copilot, Claude, ChatGPT, disparate configuration pieces are more connected to each other and to the Developer / Solution Architect sitting in front of the screen on a random Tuesday midnight.

So from a bird’s eye view of things – here’s what is more cohesive, AI-powered and in control which I plan to write further in this series and connect it all together as we sunset 2026 in these relatively newer Agentic development years.

  1. Metadata, Configuration: Dataverse MCP on your AI tools like Claude.
  2. CI/CD: Power Platform Pipelines, Azure DevOps
  3. C# Plugins and Code: Claude Code, GitHub Copilot
  4. End User Guides / Documentation: Claude Design, Figma, Copilot in Office Apps

So in the new few weeks and month, as AI continues to ever-evolve, I’ll share with my audience a framework of bringing together all the applications together with AI to deliver the same high-quality CE applications in an agentic-way.

And it doesn’t stop there – probably years after, there would be something else to replace it. But till then, this areas continue to evolve and take shape bringing from my experience and feedback from the teams and customers I work with in this remaining decade.

Hope this was helpful!

Thank you