Year: 2026

AI in Dynamics 365 CE Applications: Transforming Solution Architecting

priyeshwagh777 AI Thought Leadership , , , ,

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!

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

AI in Business: Starting Your Automation Journey [A Preface]

priyeshwagh777 AI Thought Leadership, microsoft copilot , , ,

So in 2026 as I write this, AI is intrusive to the point that everyone in Management want it because it is believe to work 10x and reduce costs or because everyone is implementing so must we.

And the predicament doesn’t stop there – it continues expand to a point where plans are chalked out to run a department entirely. And organizers scramble to solve the problem directly by introducing AI as a form of “automation” rather than “augmentation”. I pondered on this a lot and this is what I think of it as it stands today.

Although most organizations are way ahead with working AI solutions already and are monitoring for production performance and tuning. But this blog is focussed on someone who’s just arrived to AI conversations and have burnt their fingers in some POCs maybe. Here are my two cents –

Foundation of AI for Business Applications

Here’s how you start – and it’s not building your first agent directly. But are the systems hygienic for your first AI agent to not struggle? Here’s what I mean by that –

  1. Clean your data – Make sure missing Sales or Operations data isn’t cluttering your system, giving unclean and unreliable reporting. Does management completely trust the reports you run today? Get the data right.
  2. Connect your systems – Integrate systems together for not everything – but enough to make sure you don’t duplicate, miss data or rely on manual labor prone to making mistakes. If integrated, make sure integrations work well.

Now extrapolate this at the Org level and you already are starting on a high-trust metadata and data at your org for any AI agents to make sense on.

How to introduce it?

Now that data is clean and systems are connected –

  1. Start small – introduce AI in micro-tasks of your workflows. Use it to generate what your team does obviously. The routine, mundane updates. Repeating tasks which can draw patterns.
  2. With those patterns – form the knowledge base of the AI. Improve AI to feed off of the knowledge base itself. It could be a structured prompt engine or a library that the model has to traverse, process the documents and make sense.
  3. Don’t use it for decision making – use it yourself so you can make a decision – just quicker.

Why do we feel it is not what it is meant to be?

I started off by thinking in a straight line –

  1. I want to get to point B from point A – so, let me implement it and give it to the tech team to do it with some instructions.
  2. Well, it does work – most times. But I’m still not happy with it. And here is the reason –
    1. No matter how perfect the answer is.
    2. Your judgement in that moment will override always — a confirmation bias or a change in situation suitable at that point in time will make more sense.
    3. You tend to take your decision overriding what AI has to offer for you (or rather recommend).
  3. And you dismiss it saying – “It doesn’t work”.

Well, it does work – but it’s giving you an opinion so you could extend yours. It’s not meant to give you your answer, yet. And this is true for most cases if not all.

It’ll be interesting to see how this blog either ages like milk or like wine in coming years. 😊

With this, I kick-start my AI Thought Leadership as a new section and running commentary as I work to get our customers and partners ready and thriving on AI in coming years.

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

Power Apps Vibe Coded Experience [Preview]

priyeshwagh777 Power Platform, Power Platform Admin Center , , , ,

Coming from Canvas Apps to a full-fledged vibe-coded solution is the next thing in Power Platform. Let’s see how you can quickly turn things around for your team.

Let’s see how we can do this and what by Microsoft is on offer —

Power Apps Vibe Experience – What is it?

This is a vibe-coded experience provided by Power Platform to provide you a way to quickly prototype any department/use-case based application quickly and roll it out to users.
Here’s how we do it –

Pre-Requisites

  1. Assuming you have Admin access to Power Platform Admin Center, make sure that Copilot in Power Apps (preview) is turned On.


  2. Then, go the the Environment Settings as below then to Features.


  3. Once in Settings, look for Features and look for Enable External Models.


    And here’s the Enable External Models which need to be turned on.

  4. Then, navigate to https://vibe.preview.powerapps.com/ to enter the Vibe Coded Experience. And you enter the Portal directly.

  5. Start by describing the App through a prompt like this based on your use case –


  6. Then, it starts to prepare the App and also shows you the progress. The experience will also ask any relevant questions along the way.


  7. Once it has everything it needs, it’ll take you to the progress screen where you’ll see the App being made –


  8. Once the creation of App is created/completed, you’ll see the Plan mode where it describes what the App contents are.

  9. Then, in the Data mode below, you’ll be able to see an E-R diagram and also be able to Add more Tables and then establish relationships to further continue describing the App.

  10. And finally, there’s the App view where you can test the App on the fly with actual data that is connected.

  11. And then you can finally Publish this App.

  12. It’ll show how the App Publishing goes in progress.

  13. And once the publishing is done, you’ll see it this way ready to be used.


    In the upcoming blogs, I’ll show case how these can be used and deployed and embedded into.

Here’s what the Microsoft Documentation says – https://learn.microsoft.com/en-us/power-apps/vibe/overview?WT.mc_id=DX-MVP-5003911

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!

Invoice Schedule Types in Project Operations

priyeshwagh777 CRM with .NET Web Applications, Project Operations ,

Blog Post coming on 6th April 2026!

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!

Time Entry Delegation in Project Operations | [Preview Feature]

priyeshwagh777 Project Operations , , ,

While being out of office, doesn’t it scare you that you missed doing entries for the week and only you need to do it?
Well, now you can plan in advance and let others create Time Entries for you while you cannot.
This is a production-ready feature and here’s how you can use it!

Enable Delete Time Entries Feature in Project Operations

As a System Admin with correct rights, here’s how you enable Time Entry delegation like any other Project Operations settings –

  1. Go to Project Parameters, look for Features and you’ll find one for Time Entry Delegation

  2. Now, it’ll ask you for confirmation.


  3. Then, once this is setup. Notice how the My Work section doesn’t have a Time Entry delegation available previously.

  4. And when you refresh, this area gets added.

    Now, you are all set to add someone else as your Delegate.


Add a Delegate

When you see the Delegates area in your My Work section, add a record –

  1. Create a new Delegate record. Select the person who should enter Time Entry on your behalf.

  2. Enter the rest of the details i.e. From Start Date to End Date to control this delegation.


    Now, this is done. Within this time period, they can enter time entries on your behalf!

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!

Price Override in Project Operations | Part 2 [Understanding Change Amount effect]

priyeshwagh777 Project Operations , ,

Continuing from Part 1: Price Override in Project Operations | Part 1 [Inconsistent Price Update], let’s look at the Pricing.

  1. When you entered $250 for the Price Per Unit – you assumed it will update the price to $250 from $225

  2. And what you got it this – $475


Here’s the catch!

Although the wordings of the field convey that it’ll be updated to the absolute price you entered, rather it “added” to the existing Price!!
Hence, 250 + 225 = 475.

So, don’t make the mistake of assuming it’s asking for ‘new price‘, it’s actually asking you ‘how to much to increase or decrease the price by‘

Hope this was useful!

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!

Price Override in Project Operations | Part 1 [Understanding Change Amount effect]

priyeshwagh777 Project Operations , , ,

So, often times if you are working on Project Contracts, you must have encountered this button which creates a separate Price List for the Quote itself – Project Contract Price List Defaulting Behavior in Project Operations

But here’s how to track and find what happens to these Price Lists and what Price Override levels are –

Creating Price Overrides

  1. Here’ where you can find the Prices to be overridden on a Price List level –


  2. Now, when a new Quick Create form is created, you can fill in the details for either the new Price or the % and the Scope.

  3. Now, when you add the Price Per Unit, also notice that there’s a Scope field as well. Notice the types of records for the Scope defines at what level should this take effect.


  4. Let’s select an Account and save.

  5. Now when I save the record, notice that the Price is added differently.


    So, let me demystify this Part 2 of this post here: Price Override in Project Operations | Part 2 [Understanding Change Amount effect]

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!