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