AI Thought Leadership

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

priyeshwagh777 AI Thought Leadership, Dynamics 365, dynamics 365 customization, Microsoft PowerApps

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

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