Code Apps - Office Hours December 2025 Highlights
This week, the Power Apps Code gave some very useful updates at the Power Platform Code Apps Office Hours session.
Roadmap and Timeline Updates
General Availabilty (GA) of code apps is tentatively planned for January 2026. Following that will be native source control in February. After that, next on the roadmap is to support Dataverse operations like actions and FetchXML. From there, the focus will be on GCC support, invoking a flow, invoking an agent, and mobile support.
The remainder of the session focused on attendee questions.
Questions Answered
Question 1: Is it correct that with native Code Apps, we can't invoke Power Automate flows?
It's possible to call Power Automate flows but it's very awkward to do. There is no native support for Power Automate flows, meaning that we have write out own authentication logic to make the call.
The team acknowledge it's a bad user experience and are working to improve it. The opinion from attendees is that this feature is more important than auto-save to a preferred solution, and solution packager support so should be prioritised higher.
Question 2: Mobile Support for Code Apps - Is it Coming?
Mobile Support for Code Apps is coming, but it's low on the priority list. The reason is because it's still early days, and the team want to focus on making the core experience great before working on expanded features.
Another reason for it being low on the priority list is because offline support would be an important requirement of mobile support, and offine support doesn't yet exist. Therefore, this feature would need to be implemented first.
Question 3: Why Build Code Apps, rather than Canvas or Model Driven?
Code Apps brings a lot of the benefits of Power Apps but make the capabilities available and attractive to a persona who doesn't know Canvas, doesn't know Model, but loves code. It provides another offering for those wanting to build Power Apps.
Question 4: How to solve App Timed Out exceptions when connecting to Dataverse?
The most likely cause ia a failure or error with calling initialize before carrying out data operations. The "connect to Dataverse" section in how-to documentation shows how to properly initialize the SDK.
Question 5: Can we share and play apps from the solution view?
This feature request is in the backlog.
Question 6: What are the best practices for deploying across tenants?
The best recommendation for deployment across tenants or environments is to use connection references. It's necessary to use Dataverse solutions. When doing an import, the connections that the solution use will need to be in place.
In terms of logging, there is a how-to coming this week for how to add logging using pac codeapp add-datasource. We will be able to collect all the telemetry in great detail into a file.
The use of Environment Variables is good practice. Right now, if we want to pull environment variable values, we should use a Dataverse table and just pull it out of Dataverse for the time being. Further enhancements to Environment Variables are planned.
Conclusion
This meeting was very encouraging, well done to the Power Apps team for the developments so far. It's very promising to see some plans for key areas being discussed, such as Power Automate integration and mobile support.
