Power Community

Power Community

Model Driven Power Apps

Power platform Developer tools May Refresh

We are delighted to announce the release of our new update (Version: 1.16.5+gba7d6a4) for the Power Platform Command line. This May refresh comes with capabilities ranging from support for single sign-on to even simple things like showing whether solutions are managed or unmanaged when listing out the solutions. So, without further ado, let us get into the details. Single Sign-on (Early Capability) In this new update, when you don’t provide a URL, it creates a universal single sign on authentication profile and authenticates you to your default organization. This is an early single sign-on capability, we plan to improve on it further in the upcoming updates. So, when you use the `pac auth create` command and not provide anything else or `pac auth create -dc` without additional parameters, it will create a new authentication type called universal. You can still authenticate to other dataverse environments, using the –url parameter. But we would really like to get your feedback on this new single sign-on capability. Please let us know what you think. Support for China Sovereign Cloud From PAC CLI we have added support for Azure China Sovereign cloud, this was a long ask from our China based customers and now we can use Power Platform command line capabilities to the China cloud as well. This also means GitHub actions are also supported in the China Sovereign cloud region and eventually we will also support Azure DevOps actions. Here is an example of how you if the China Cloud is supported Support for Packages that hold .cab files We introduced a bunch of new changes to the `pac package` command in the last update, As in now packages can also be build just like a solution, except in packages I can bundle multiple solutions and deploy. Now can you deploy packages that *.cab files Showing if solutions are managed or not on the command line One of the most frequently asked features by our user community by far. We now have the ability at the command line to know if a solution is managed or unmanaged. In the past the only way a user would know if a solution was managed or unmanaged was when they did an export and the export error out saying the solution was managed. Now when you do a `pac solution list`, you get a column identifying whether the solution is managed or unmanaged. As you can see we have been adding more capabilities to the CLI. Our team has been actively working on making our Azure DevOps tasks to also be based on the Power Platform CLI, instead of the current PowerShell modules. We will be pushing out that update in early July, and in most cases those that are using your existing Azure DevOps pipelines should not notice any difference. The benefit of this work is that both GitHub actions and Azure DevOps tasks will be powered by the same engine and be cross platform. As always, we are excited to bring these capabilities to you. If you have additional feedback please reach out to us via the following forums ISVFeedback@Microsoft.com or The PowerUsers community. Raise the issue and bugs at the following location in GitHub https://aka.ms/powerplatform-vscode

Power platform Developer tools May Refresh

We are delighted to announce the release of our new update (Version: 1.16.5+gba7d6a4) for the Power Platform Command line. This May refresh comes with capabilities ranging from support for single sign-on to even simple things like showing whether solutions are managed or unmanaged when listing out the solutions. So, without further ado, let us get into the details. Single Sign-on (Early Capability) In this new update, when you don’t provide a URL, it creates a universal single sign on authentication profile and authenticates you to your default organization. This is an early single sign-on capability, we plan to improve on it further in the upcoming updates. So, when you use the `pac auth create` command and not provide anything else or `pac auth create -dc` without additional parameters, it will create a new authentication type called universal. You can still authenticate to other dataverse environments, using the –url parameter. But we would really like to get your feedback on this new single sign-on capability. Please let us know what you think. Support for China Sovereign Cloud From PAC CLI we have added support for Azure China Sovereign cloud, this was a long ask from our China based customers and now we can use Power Platform command line capabilities to the China cloud as well. This also means GitHub actions are also supported in the China Sovereign cloud region and eventually we will also support Azure DevOps actions. Here is an example of how you if the China Cloud is supported Support for Packages that hold .cab files We introduced a bunch of new changes to the `pac package` command in the last update, As in now packages can also be build just like a solution, except in packages I can bundle multiple solutions and deploy. Now can you deploy packages that *.cab files Showing if solutions are managed or not on the command line One of the most frequently asked features by our user community by far. We now have the ability at the command line to know if a solution is managed or unmanaged. In the past the only way a user would know if a solution was managed or unmanaged was when they did an export and the export error out saying the solution was managed. Now when you do a `pac solution list`, you get a column identifying whether the solution is managed or unmanaged. As you can see we have been adding more capabilities to the CLI. Our team has been actively working on making our Azure DevOps tasks to also be based on the Power Platform CLI, instead of the current PowerShell modules. We will be pushing out that update in early July, and in most cases those that are using your existing Azure DevOps pipelines should not notice any difference. The benefit of this work is that both GitHub actions and Azure DevOps tasks will be powered by the same engine and be cross platform. As always, we are excited to bring these capabilities to you. If you have additional feedback please reach out to us via the following forums ISVFeedback@Microsoft.com or The PowerUsers community. Raise the issue and bugs at the following location in GitHub https://aka.ms/powerplatform-vscode

Announcing general availability of our new Dataverse experiences on Power Apps

When building apps, data is usually the core of your experience – and Dataverse is a natural solution for Power Apps. Dataverse gives us a huge breadth of features to work with so we’ve been investing in familiar and intuitive experiences for our users, so that they can get the best out of Dataverse. This week we announce the general availability of our new data focused experiences and we’re excited to give you a tour of the changes here. Updated list of tables When diving into tables you often want to see what’s already available or find previously used tables to continue to edit. We’ve updated the list of tables to make it simpler to find what you need with extensive support for filtering, sorting, search and have provided some key pivots on this list. We’ve also grouped the table commands in familiar ways to make it easy to find the option you’re looking for. The biggest change you’ll notice here is that tables can now be both Opened and Edited. Opening a table will navigate to the table hub and Editing a table will take you to the new full-screen table designer – we’ll have a look at both of these next! Table hub When you open a table, you’ll see a hub layout giving you an overview of the table with its properties and grouped links for related table components (like forms, views or columns). You’ll also see the top 10 rows of data for the table with controls to include other columns that already exist. This view lets you simply update data in a spreadsheet-style mode, and just like a spreadsheet you can quickly add new columns here too. Diving into related table components, like columns, gives you the detail list of those items, with the same powerful sorting, filtering and searching. And to avoid jumping back and forth you can now switch between these lists with a dropdown in the breadcrumb. Table designer When you need to dive into the full data set, you can edit the table in a full-screen experience that gives you access to all the data in the table (of course, limited by the security roles you have!). For those that are more familiar with side-pane experiences around the Power Platform, you can also use the left pane in this view to manage which columns appear on the table as you edit. Create an app quickly Now that you have found or built your table, it is just one-click away to create a new modern app over that table, whether you’re on the table hub or in the full-screen experience – all you need to do is provide a name for your app and we’ll automate all the steps necessary to create the app, add your table to the sitemap with all forms and views available, and bring you into the modern app designer. What’s using this table? Often tables of data support many apps and flows, so to quickly find out what your updates to a table might impact, you can select a command on the table hub to view the list of apps and flows that are Using this table. There is also a quick way to play or edit the apps and flows you find from this view. Columns, data types and formats With this update to tables experiences, we have also focused on columns as they are key to storing meaningful data – the majority of columns created are text, whole number or date/time so these are all readily available in a single-click. However, we know other data types are key to many scenarios, and those can even have multiple formats. We’ve organized these data types and formats in an easy to work with way, as well as adding search to the menu. Formats can now be updated after the column is created (switching between formats in the same data type), we have introduced a new format for text types called Rich text that allows you to store and work with rich data in your apps. Advanced options are hidden by default but if you need to tweak some of this column properties you can expand that section of the panel to access all the other properties that columns support. Choice columns Providing users with a set of choices can really improve an app’s data entry experience and ensures that users are picking from a set list of items. We’ve enhanced the management of these column types to make it easy to sort, drag/drop reorder, set colors and get access to all the other properties of the choice, including support for extending out-of-the-box Status Reasons. Advanced table tools For those makers that are further along their journey with Power Apps and Dataverse, they are often looking for underlying table and column names for their code or integrations, so we’ve added Tools that will copy these names to the clipboard and allow you to open tabs to the table definition or data query APIs. When working with the table in a solution you can browse tables in parent solutions of patches, and you can also review/update managed properties for both the table and all the related table components that support managed properties.

Announcing the general availability of Power Apps modern commanding

Casey Burke, Senior Program Manager, Thursday, June 2, 2022 We’re very excited to announce modern commanding with Power Fx is now generally available (GA). Modern commanding provides a maker friendly low-code/no-code experience for customizing model-driven app command bars – with the first ever in-product command designer and the ability to use Power Fx (or JavaScript) for expressing business logic. Modern commanding has many improvements since the preview was announced last year. We sincerely appreciate the overwhelming amount of support and feedback from the Power Platform community and the close partnership with Scott Durrow (Microsoft MVP and Ribbon Workbench creator). This has helped shape the below goals and GA features. Makers love the experience A large number of usability and maker productivity improvements have resulted in a simpler and streamlined maker experience. A few highlights include the addition of copy + paste, optimized navigation & layout, drag and drop within command designer, performance improvements, and deferring creation of command component libraries. Do more with Power Fx Various new functions are now available to better support common command use cases. Defining visibility, actions, and interacting with custom pages is now much more powerful. For example, control command visibility using RecordInfo() and DataSourceInfo(), and work with unsaved data (aka the buffer) using Self.Selected.Unsaved. No cliffs Many parity gaps with classic Ribbon commands have been closed (+ a ton of new goodness not previously possible). For example, now you can create dropdowns, split buttons, and groups as well as specify different scopes – which determine whether a command is published to a single app, to a table and all apps using it, or even globally to all apps and all tables. These new scopes prevent duplicating effort for commands that need to be present in multiple apps. As an added benefit, when citizen developers modify or hide broader scoped commands, their changes are automatically isolated within their app and other apps remain unaffected. Rock solid reliability and ALM The most important improvements are not typically visible. We’ve made significant investments into strengthening the modern commanding infrastructure, fixing issues, improving performance and reliability, and ensuring application lifecycle management is handled consistently. GA is a milestone, not an end state. There’s much more we’d like to do and while I can’t share everything just yet, here’s a few improvements coming soon: Editing Microsoft first party (OOB) commands using modern command designer. We realize this limitation is especially painful and have been working diligently to solve this complex problem reliably. Classic OOB commands will be incrementally migrated to the modern commanding infrastructure. Migrated commands will be fully supported in command designer. Migration will not impact existing customer customization or the ability to continue using classic capabilities. We’ll later provide an easy button to migrate your own classic commands. Support for classic enable rules, display rules, and custom rules. Supporting additional Power Fx functions and improving the publishing experience. Addressing other known limitations. Check out the modern commanding documentation as well as the recent Power CAT Live interview with Phil Topness, Prabhat Pandey, and Casey Burke.

Announcing the general availability of canvas components and component libraries

Hemant Gaur, Principal Program Manager, Wednesday, June 1, 2022 Today, we are excited to announce the general availability (GA) of canvas components and component libraries. 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 ALMMakers 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. Component library ALM support. 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, Add images to component Custom pagesCanvas 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

New: turn images and designs into apps using AI-powered express design

we’re thrilled to announce the preview of :directly from design files and images. In just a few clicks, customers can now create web and mobile apps from a broad range of inputs—including paper forms and PDFs, sketches on the whiteboard, and even professionally-designed assets in Figma. Express design adds to the many ways in which Power Platform is applying advanced AI to assist more people in driving innovation for their teams and businesses. According to IDC, more than 500 million apps and services will be built in the next five years, more than all the apps built in the last 40 years.1 This demonstrates the speed at which organizations and developers need to be adapting. We’ll only achieve the pace and scale we need if we can continue to shorten the distance between a challenge and a solution. This is where express design can help, by making it much faster to turn an idea or an existing asset into a working application.  Create apps instantly with express design Power Apps express design is like an AI-powered copilot helping create apps alongside you. Here’s how it works: Get going with a variety of content types: tart with a paper form, PowerPoint, PDF, a screenshot of a UI from a legacy app, or even a picture of a hand-drawn app that you’ve sketched out on paper. Or point to a design file in Figma.  Advanced AI will scan your file: Using cognitive AI models that are trained to recognize common application elements, Power Apps will automatically generate an app with a working user experience and data schema in Microsoft Dataverse. Tune the model to get exactly what you need: From the AI-generated starting point, make quick inline adjustments. Need a dropdown control, or maybe a date picker? No problem. Seamlessly connect to all of your data: Easily adapt and configure the application using low code. Use more than 675 prebuilt connectors to integrate with your existing systems including SAP, Salesforce, and SQL. Add as many screens as you like: If you want to add more screens to the app, simply upload additional files, or create them easily in the low-code Power Apps Studio. Express design helps accelerate many common scenarios that hold back digital transformation today. Just a few examples include: Modernizing legacy and paper forms. Many organizations still have outdated libraries of paper and PDF-based forms and processes and don’t have the resources to effectively modernize and move them to the cloud. Now, these forms can quickly and easily be converted into digitized solutions by those closest to the business process, and not just with a pre-built UI, but with a pre-built data schema on an integrated data platform. This will not only save time, free up developers to focus on strategic work, and reduce manual errors, but it will also accelerate the organization’s move to the cloud, ensuring this data is secure and can be used to unlock additional insights. Generating apps from sketches and wireframes. It has never been quicker or easier to go from idea to app. From whiteboard ideation sessions to PowerPoint brainstorms to a hand-drawn sketch, just capture an image of your idea and see it quickly brought to life in Power Apps. Accelerating professional design and development. We’re particularly excited about our integration with Figma, the collaborative design platform, where so much software is designed today. It can be challenging and time-consuming for developers to replicate the UX that designers have already created in the design tool. Now with express design, designers can create designs using the Power Apps Figma UI Kit and developers can convert that design to a functional app in moments, significantly speeding up the design to the development process, as well as eliminating multiple feedback loops. Figma to app bridges the gap between designers and developers to deliver an optimal experience for the end-users, saving significant time as well as providing more control over the end-to-end build experience. Learn more about administering Microsoft Power Platform.  Power Apps continues to advance AI-assisted low-code app development Unlike other design-to-code tools, express design provides a major step forward by generating a true low-code app that any maker can easily customize, extend, and connect to hundreds of pre-built and custom data connectors. By using advanced cognitive AI models to understand the intent behind an image—including the structure of a form, controls, and data—express design is far more versatile than any single integration with a particular program or format. Express design is just one of the many ways that Power Platform is accelerating the development cycle using AI to assist a wider range of human developers. Express design builds on the advanced natural language to code and programming by example capabilities we announced last year at Ignite, and we’ll continue to invest in innovative capabilities that help all makers achieve more. Get started now Express design in Power Apps is included for all makers at no additional cost, so it has never been easier to get started. Already have Power Apps? Try out express design today. Need a free developer plan? Get started here: Power Apps Developer Plan. Want to try Figma? Get started here: Figma. 1-IDC FutureScape: Worldwide IT Industry 2020 Predictions, IDC.

Announcing the general availability of the Power Apps modern app designer

Jessica Lo, Program Manager II, Thursday, May 19, 2022 We are excited to announce the general availability of the modern app designer, enabling a seamless, intuitive way to build robust model-driven apps with Dataverse grids, forms, and custom pages with just a few clicks. The modern app designer is now the default designer for model-driven apps and is at full feature parity with the classic designer. The modern app designer has a live preview where you can directly interact with content of the app, resize to see the app on different screen sizes, add custom pages, and many more! The preview of the modern app designer was announced around June of 2021. Since then, we’ve added many new features, as well as improved the current experience based on feedback received from the community. We’ve made lots of improvements and will continue to do so after general availability to make the designer the best that it can be. New features added in the modern app designer include the ability to add custom pages, business process flows, Power BI dashboards, interactive dashboards, new areas, URLs/web resources as a subarea, customize sitemap icons, locales, app tile icon, and manage chart views. The modern app designer is the foundation for many more exciting features in the app authoring space. Therefore, we want your feedback! Let us know your thoughts and suggestions in the community, and please visit our documentation for more information. Happy building!

Access Migration to Power Apps and Dataverse is released to General Availability

Beginning today, Microsoft Access users can migrate their data into Power Apps and Dataverse.  Customers who have the current or monthly channel for Microsoft 365 and Office can update their Microsoft Access to make use of the Dataverse Connector and migration tool. The Access migration tool and connector provided within MS Access streamlines the process of migrating tables, relationships, and data with setup taking just a few minutes, and migration handled for you. Figure 1. Access, Dataverse, and Power Apps With the GA of this feature, Access customers are now one-click away from unlocking the following capabilities for the data currently managed in an Access DB: New security and compliance capabilities through Dataverse cloud storage using Azure Active Directory and role-based security while managing it from Access The ability to have real-time sharing and editing of Access data using cloud-based data stores, with front-end apps created in Access, Power Apps Mobile and Microsoft Teams  New front end app scenarios on mobile devices or with Microsoft Teams Extending the ability for users to incorporate their existing data into Power Apps and Dataverse is an important feature. Almost every user who starts working with the Power Platform begins with existing data. By offering easier ways to migrate Access data to Power Apps, customers can implement apps, workflows, virtual agents, and perform analytics on data that was previously not available to them. The Access data will behave like any other Dataverse data once migrated. In addition, user’s Access forms and queries will continue to work uninterrupted, allowing a migration without business disruption. Figure 4: The workflow of migrating data from Access to Dataverse, with synchronous usage by Access forms and Power Apps. Today’s announcement expands and enriches the cloud story for Access and continues Power Apps and Dataverse’s commitment to helping users incorporate their existing content to enrich their business. Take the next step to migrate Access data to Dataverse and the Power Platform To test out this new capability you will need to have an existing Power Apps trial environment, Power Apps license, or Power Apps installed as part of your Microsoft Teams license. Talk to your administrator to confirm if your organization is on the current channel as of May 2022 for Microsoft 365 and try the new Dataverse Connector. Once you have updated your Access application, you will be able to start migration from within Access by right clicking a table and selecting Export and Dataverse. Figure 2: The Export menu in Access with the Dataverse option You can also open a table, select the External Data tab on the ribbon, and select Dataverse. Figure 3: MS Access Ribbon with Dataverse Export button Dataverse Options Users will have the option to migrate their Access data into Dataverse or Dataverse for Teams, allowing them to choose the capabilities that best suit their needs. Dataverse provides the full featured extensibility of the Power Platform providing citizen developers and development professionals alike the power to explore the possibilities of their data and share it across their entire organization, or externally using Portals. Dataverse for Teams provides the ability to create apps, flows, virtual agents and more within a team structure using Microsoft Teams, the collaboration tool of choice for the modern enterprise. If you are interested to take the next step and evaluate this powerful combination yourself, visit https://aka.ms/AccessAndPowerPlatform. For support documentation on how to migrate go here To learn more about these capabilities register for Microsoft BUILD and see two different on demand sessions that educate and demonstrate these capabilities. BUILD Session # OD122 – Title: Access Connector for Dataverse and Power Platform GA Launch BUILD Session # OD123 – Title: Pro developer capabilities of Power Apps and Dataverse for Access Developers

Updating ownership for Power Apps apps

Recently, a customer asked a question that we felt would be applicable to many of you responsible for administration of the Microsoft Power Platform: How does removal of an app owner’s profile from Azure Active Directory (AAD) impact access to the app? Before we answer that, you need to know that in Microsoft Power Apps, there are two different application types: Model-driven apps Canvas apps Model-driven apps and canvas apps manage their ownership differently. In this blog post, we’ll explain how to update ownership of each type of app. Note: If you need more background information about the two types of apps, watch The difference between Canvas Apps and Model Apps – YouTube or review Start building apps – Power Apps | Microsoft Docs and Power Apps architectural design – Where to place logic – Power Apps | Microsoft Docs Model-driven and Canvas apps manage their ownership differently. Model-driven app ownership In a model-driven app there is no concept of a co-owner. If the original owner/creator leaves the organization, what happens to the application? Users who already have the app shared with them can continue to use it. What if an update or maintenance is required? Well, our admins can help us here. Users with the role of System Customizer, System Administrator, or Environment Maker in the environment can manage the application but they don’t technically “own” the app. What happens when the owner leaves? Ideally, the owner would work with the organization during their outgoing knowledge transfer sessions: explain what it does, what are the use cases, who is the user-base, and hand over any documentation to a new owner. To change the ownership though you will need to export the application and re-import it under another user. If they leave without being able to do this, then admins noted above can do this. Deleting or removing the owner won’t have any impact on the performance of the app itself. For more information, see Model-driven app FAQ – Power Apps | Microsoft Docs. Below are some common questions relating to ownership and changes: Q: How do you change the owner? A: Export the app and re-import it as under another user. You will need to re-share the app to the users. Q: What happens if the original owner leaves? A: Users who already have access to the app can continue to use it. A: Ideally, the owner would work with the organization to export the application, explain how it operates and hand over any documentation. Q: What happens if we need to update the app? A: Admins can help here. Users with the role(s) of System Customizer, System Administrator or Environment Maker can manage changes to the application. Q: What happens if the owner’s account is deleted? A: Deleting or removing the owner won’t have any impact on the performance of the app itself. Canvas apps ownership Canvas apps, unlike Model-driven apps, can be co-owned or have the owner replaced. If an owner is leaving, they can share the app through the Maker portal. Note that this ownership change does not affect the users with whom it is shared. For more information please see: Manage Power Apps – Power Platform | Microsoft Docs On the other hand, if the owner of the app left without adding a co-owner an admin can change the owner through PowerShell. First, you will need Tenant Admin access. You will also need the Environment Id (envId) and App Id (appId). You will also need to specify the user Id; in this example we will change the ownership to your Id. Second be sure you have the Power App cmdlets installed. You can do this with the following commands. Run PowerShell in admin mode and enter: Install-Module -Name Microsoft.PowerApps.Administration.PowerShell Install-Module -Name Microsoft.PowerApps.PowerShell – AllowClobber If you already have the cmdlets installed, nothing will occur and you are good to go; otherwise, you will see the cmdlets installed. Next, run the Add-PowerAppsAccount cmtlet allowing you to add your account for Power Apps: Add-PowerAppsAccount Next, update the owner, using the appId and envId you found earlier: Set-AdminPowerAppOwner -AppName "" -EnvironmentName "" -AppOwner $Global:currentSession.userId When this command succeeds, the response is minimal, showing only a reference to app Id. The app is now “owned” by the new user. Reference documentation for the PowerShell commands: Add-PowerAppsAccount (Microsoft.PowerApps.Administration.PowerShell) | Microsoft Docs Set-AdminPowerAppOwner (Microsoft.PowerApps.Administration.PowerShell) | Microsoft Docs

Announcing New Data Sources for the Virtual Connection Provider

I am happy to announce that we are adding Excel and SharePoint to the virtual connection providers for virtual tables. You may have used the SQL virtual connection provider during its public preview, based on popular requests, we have enabled the same functionality for two of the largest external data sources for Power Apps. 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. 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
- Advertisement -spot_img

Latest News

- Advertisement -spot_img