What’s new since preview?

While the most impactful improvements are better reliability, performance, and usability, there’s many new and noteworthy capabilities.

• Disconnect from Git – You can easily disconnect your environment or solution from Git and reconnect to a different source code location or branch.
• Support for existing solutions and large solutions – These critical preview limitations are now addressed. Connect existing solutions in your environment and you won’t be limited by solution size when committing large solutions.
• Public API’s – Now you can interact with Git using Dataverse API’s and build automations to scale the process.
• Support for more object types – most solution components are now supported and we’re incrementally onboarding the remaining legacy components / objects.
• Delete when pulling – when an object is deleted in Git, you now have the option to delete it from your environment or remove from your solution on pull.
• Better user experiences – Git integration is available in Copilot studio (and other maker portals), with improved discoverability, usability, and columns showing who changed what and when.
• Geo availability – Git integration is GA in all public geos and coming soon to sovereign clouds.

Source Control your Canvas Apps

Dataverse Git Integration is the new standard, replacing the experimental Power Apps integration. If you’re still using the old setup, we recommend migrating to the new integration as soon as possible.

With Dataverse Git Integration, you get complete visibility into your source code – no conversions required. You can use pa.yaml files in your repository to manage source control and review changes made in Power Apps Studio, all without the clutter of noisy diffs.

The schema for canvas source code (pa.yaml files) is now published, and no breaking changes are anticipated moving forward.

What’s next?

General availability doesn’t indicate a feature is done – or that it’s without limitations. Rather, Microsoft is confident in the quality for production use. It’s important to evaluate whether current functionality meets your requirements.

Next up is unlocking code-first development. Soon, developer tools will support the new (YAML) format, which is easier to read, understand, and merge. Modern developers can then build and deploy solutions and code from source control with less effort and without prior domain knowledge.

For canvas apps, we will also start to enable (as preview) the capability to edit pa.yaml files directly in your repository.

We’ll be showing code-first demos at Microsoft Build next month, plus many other new and exciting Managed Operations and other capabilities.

Learn more

Setup Git Integration

FAQ

Source Code files for canvas apps

The post Git Integration is Generally Available appeared first on Microsoft Power Platform Blog.

Canvas components enable low code/no-code developers to build reusable UX components using default Power Apps controls as core building blocks. These custom components can then be shared across app screens or multiple apps both within and across Power Apps environments. Canvas components contributes directly towards Power Apps vision of empowering everyone to build apps by significantly accelerating app development process.

Following are the new enhancements which are part of this GA announcement.
Support for component library ALM
Makers can now package their apps and component libraries inside a single or multiple solutions and import them into a different environment. If a canvas app is using a component library, it is now tracked as a solution dependency. ALM support ensures that the dependency relationship is maintained in the target environment and any further library versions imported via solutions can deliver the updated components to the app. It enables 1st and 3rd party publishers to ship their components and customizable apps as baseline and then service apps by shipping just the updated component library. All standard solution actions such as managed properties, show dependencies, and add required components are supported inline with the Dataverse solution capabilities .
You can find more details here – component library application lifecycle management.

Image/multimedia file support 
You can now add multimedia files to the components inside a library. These components can then be used by all apps in an environment. Libraries with multimedia files can be moved across environments using the standard component application lifecycle management (ALM).
For details please refer to add multimedia to a component,

Custom pages
Canvas components can be used in model-driven apps using custom pages.  Canvas component library provide app makers the ability to create custom components using custom page supported set of controls which includes modern Fluent UI controls. These components can then be reused across custom pages and applications, and can be centrally updated, packaged, and moved using Dataverse solutions.
For More information see add canvas components to a custom page for your model-driven app.

Fundamentals investments – Performance, reliability and accessibility.
Canvas components have seen huge adoption across large and small organizations since our public preview announcement. Components already are being utilized heavily by hundreds of thousands of apps. We have been constantly monitoring user feedback, feature usage, errors and have been shipping weekly updates to improve feature fundamentals. Thanks everyone for helping us take feature to GA.

Looking forward to next phase of low code extensibility.

Cheers,
Hemant Gaur

The post Announcing the general availability of canvas components and component libraries appeared first on Microsoft Power Platform Blog.