It just takes a few seconds to connect your Dataverse environment to Git. You can connect and use Git integration within Power Apps, Microsoft Copilot Studio, Power Automate, and Power Pages. You’ll also need access to an Azure DevOps Git repository.

Rollout is in-progress. Git integration is currently available in public geos outside the US. Your environment must be enabled for early access and accessed at https://make.preview.powerapps.com.

As the team develops, Dataverse tracks everyone’s changes. When ready, commit your changes to a branch in the connected Azure DevOps Git repository. A commit link is provided to view the changes within the repository and compare diffs. You’ll notice solutions and solution objects are now stored in human readable formats in the repo.

Professional developers can work in source control while others work in one or more environments. It’s easy to pull others’ changes into other development environments which are connected to the same source code location. This allows team members to build without others editing in their environment and share changes once they’re ready. Connect multiple development environments using the same repo, branch, and folder. Then, in each environment create or import an unmanaged solution with the same name and publisher.

When committing and pulling changes, conflicts may be detected – meaning someone else made conflicting changes to the same object. You’ll need to choose whether to keep the version that’s in your environment or bring the version from source control into your environment. You can also revert changes in the repository, then pull the prior version into your environment.

When the team is ready to deploy to test or production, you can use Pipelines in Power Platform for the release. Building and deploying using developer tools isn’t available yet for this new format.

We hope you enjoy the preview. There are many current limitations and you shouldn’t use this feature in environments or Git folders where you’re developing production solutions. Please leave your feedback below, in the community forums, on social media, or another outlet of choice. We look forward to hearing what you’d like to see prioritized next.

Learn more

Overview of Power Platform Git integration

Setup Git integration

The post Introducing Git Integration in Power Platform (preview) appeared first on Microsoft Power Platform Blog.

Introducing smart paste

Smart paste is the latest capability of Copilot form fill assistance for model-driven apps, designed to make the time-consuming and frustrating task of form filling easier. Imagine this: you have some text in an email, document, or note that you need to enter into a form. Instead of manually typing it all in, you can now simply copy the text to your clipboard. Without selecting any specific field, just click the smart paste button or use the standard paste shortcut (CTRL+V or CMD+V). Copilot will reason over the form and the pasted text to suggested what text could be used to fill specific fields, and provides suggestions inline in the form. You can review and accept the suggestions that work for you—as always, nothing gets saved until you confirm. Ignoring suggestions will automatically discard it, and we are also introducing a new capability to clear all suggestions in the form.

And if you prefer the traditional way, you can still paste directly into a specific field by clicking on it first and then pasting.

You can use smart paste in your model-driven apps by updating the following two settings in Power Platform admin center, under Settings > Product > Features > AI form fill assistance section:

1. In the Enable this feature for field, make sure that All users immediately is selected.
2. Set Enable smart paste (Preview) to On.

Discover the suggestion source using new citations

We are introducing a new capability that adds even more transparency to Copilot’s suggestions. With the new citations, you can now learn more about the source of the suggestions provided by Copilot. These citations clearly identify the source, for example “Records you have updated recently” or “Clipboard”, giving you more clarity and confidence in the suggestions you receive.

Form fill assistance now available in quick create forms

Form fill assistance, including the new smart paste capability, is now available in quick create forms as well. This means you can enjoy the same time-saving benefits across even more of your forms.

Expansion to 21 languages

Form fill assistance in model-driven apps is rolling out in the following 21 languages in addition to English (US):

1. Arabic
2. Chinese (Simplified)
3. Czech
4. Danish
5. Dutch
6. Finnish
7. French
8. German
9. Greek
10. Hebrew
11. Italian
12. Japanese
13. Korean
14. Norwegian (Bokmål)
15. Polish
16. Portuguese (Brazil)
17. Russian
18. Spanish
19. Swedish
20. Thai
21. Turkish

We want to hear from you

Learn more about this feature in the documentation. We look forward to you trying out these capabilities in your model-driven apps and sharing your feedback through the form fill assistance survey in your model-driven app.

The post New smart paste makes filling forms as easy as copy & paste appeared first on Microsoft Power Platform Blog.

What are Virtual Tables?

Virtual tables connect to existing data outside of Dataverse allowing Power Apps and the Power Platform to treat it like local data. If you have a list that stores all of your product data in SharePoint, a virtual table lets you access that data within an app and also provide relationships between Dataverse tables and the SharePoint lists. You can even use your custom Power Apps code to make changes directly in the source, just by using the APIs that Dataverse provides.

Virtual Table Components

Virtual tables require connectors and connection references in order to authenticate to the data source and allow Dataverse to speak to the connection. If you are building a virtual table manually, you need to build plug-ins to allow the Dataverse and source APIs to communicate, set up a connector, set up a connection reference, register a service principle with Azure to allow authentication, and then finally build the table.

Why are Virtual Connector Providers important?

Virtual Connector Providers make the process of creating virtual tables easier. If you use a Virtual Connector Provider, Dataverse does some of the work for you. You will no longer need to:

• Create Plug-ins for APIs
• Create Service Principles
• Search for which tables or lists are compatible in your data source

All of these steps are handled for you!

Entity Catalog

The Entity Catalog will provide you a listing of every table or list from a connected data source that can be used for creating a Virtual Table. This reduces the creation time by eliminating the need to search for the exact table or list names in your source. The catalog is created automatically once you connect to the Virtual Table source.

Note: If you have used the virtual connector provider for SQL you may notice some changes. Creating the virtual entity source no longer requires details like Client ID and GUIDs as this is managed by Dataverse.

When is this available? NOW! Feel free to try it out. Check out our online documentation for more details.
Important note: At this time there is a required step to download and install the Virtual Connector from Appsource. This will not be needed in a few weeks from now. Since this is temporary it is not included in the video walkthroughs. The process for doing this is covered in the online documentation.

Also, you can watch 4-minute, step by step videos for each virtual connector provider:

Create a Virtual Table for SQL with the Virtual Connector Provider
Create a Virtual Table for Excel with the Virtual Connector Provider
Create a Virtual Table for SharePoint with the Virtual Connector Provider

The post Announcing New Data Sources for the Virtual Connection Provider appeared first on Microsoft Power Platform Blog.