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.

Data Stewardship to Scale

The most inspiring reason for learning Dataverse is the breadth of capabilities you can use to set strong standards for data stewardship. As per Wikipedia: “Data Stewardship means the formalization of accountability over the management of data, and the data-related resources. So, while data governance programs set the rules, data stewardship oversees the smooth implementation of those rules.” Therefore, data stewards seek a comprehensive approach to data management to ensure the quality, integrity, accessibility and security of the data.

How does Dataverse help? Dataverse is designed to be more than just a database. It can also include data from other data sources, for example through virtual tables. Everyone can take advantage of the built-in Common Data Model (CDM) tables designed to support strong communications between you and the businesses you partner with. Of course, you can also easily create custom tables, views, and forms. But don’t stop there! Take the data model to the next level by layering business logic, rules, and process flows to maintain data integrity and guide participants through important process steps or milestones. This end-to-end approach of optimizing enterprise data models enables both solution makers and business analysts to use, and to share data, with confidence.

Get started right away extending the value of tables and leveraging business rules with the new “Formula Fx Column“. The Formula Fx Column enables us to use Excel-like expressions within table columns (aka Power Fx). In the solution below, I’ve added a column to check when the current contract value exceeds 30% of the original bid value. Now Dataverse will trigger process alerts through Power Automate when this occurs. Since the logic is built into the data, all the Makers (new and old) will automatically gain this logic when they build apps using this table; no matter what type of app they build!

TIP: Leverage Formula Fx columns to drive consistency in process and notifications

Granular Security

Microsoft consistently prioritizes security and customer trust. Anyone can learn more about Microsoft’s Security and Trust commitment, or specifically about security and compliance for the Power Platform. So, why do I call this out as one of the three reasons for learning Dataverse? Because Dataverse brings security to the next level with its scenario-focused approach that facilitates a wealth of data visibility, security, compliance and auditing. Dataverse manages these through several layers of controls making it a platform with security on steroids. Some of the most commonly used layers of security include, but are not limited to:

• The Environment: The environment itself is the root container in the tenant for Dataverse. So it’s easy to assign a Security Group (“SG”) to an environment. This will constrain the environment contents (such as database tables) to members of that SG.
• Column-Level Security: Each column within a record can be configured for column-level security. Now we can decide to share all Customer Account details with the Sales team, but restrict access related to contract value and invoicing to only the Finance team.
• Role-Based Security: Dataverse uses role-based security (RBS) to group together a collection of privileges. These security roles can be associated directly to users, or they can be associated with Dataverse teams and business units. Users can then be associated with the team, and therefore all users associated with the team will benefit from the role. My favorite thing about this is that you can create roles and then insert them into the Solution Package so they can easily be reused there or in other solutions.

This layered approach to security and record visibility supports the diversity of requirements needed for common business scenarios. It’s not just about ‘who can access what data’, it’s also about facilitating need-to-know visibility by combining layered security with filters and views to aid in discovery, yet reduce noise in a people-friendly methodology.

Note the roles and the people in the image below. They are all working on a construction project but they have varied data access constraints and requirements. Dataverse can ensure that each individual gets to what they need to know, when they need to know it.


TIP: Simplify, and reuse, Security Roles by storing them in Power Platform Solutions:

Extended Integration Powers

Not all of our data starts or ends in Dataverse. Dataverse is designed to help you to orchestrate all your enterprise data needs, no matter where that data is stored. In many cases we will want to migrate, synchronize with, or simply just view data virtually within Dataverse.

Both migration and synchronization occur easily using Dataflows. Dataflows are a self-service, cloud-based, data preparation technology. Dataflows enable customers to ingest, transform, and load data into Dataverse environments, Power BI workspaces, or your organization’s Azure Data Lake Storage account. Customers can trigger dataflows to run either on demand or automatically on a schedule; data is always kept up to date.

But wait, you don’t always have to move or synchronize data! In many cases, having a “virtual” table is the best choice for leveraging the data directly from the source. Any business user can create virtual connections to data external to Dataverse. Check out the new virtual table providers for SQL, SharePoint, and Excel for example. Thanks to virtual table providers, we can now take advantage of data outside of Dataverse to layer it into our solutions, or to enable more complex scenarios that require modern technologies such as Artificial Intelligence (AI), Machine Learning (ML), Internet of Things (IoT), Azure functions, extended compute power, and/or dynamic query-driven tables.

TIP: Optimize solutions by layering data sources that you rely on every day using virtual tables

My favorite service integrations are those related to optimizing Business Intelligence (BI) insights (such as with Power BI), and the wide selection of Azure service partnerships, such as with Azure Synapse. Azure Synapse extends both compute power and our ability to create dynamic table queries through the use of Spark or SQL select statements. Both existing Dataverse tables and query tables created in Azure Synapse, provide creative opportunities for visualizations and insights in Power BI (learn more in this demo).

TIP: Take advantage of Spark and SQL Select statements along with the enhanced compute power of Azure Synapse

Conclusion

There is definitely a broad return on investment when it comes to learning Dataverse.

• Data Stewardship to Scale – helps us to reuse data and set standards across our business
• Granular Security – secures data across the domain, across tables, including column and role based security
• Entended Integration Powers – enables us to bring data from anywhere we need it into our solutions

Get started learning today:
Microsoft Learn for Dataverse
Additional resources:

1. Security Concepts
2. Power FX and Business Rules
3. Virtual Table Connector Providers
4. Azure Synapse Link for Dataverse

The post 3 Primary Reasons to Learn Dataverse appeared first on Microsoft Power Platform Blog.