Power Platform Governance and Administration

Currently, there is no out-of-box method apart from Export to Excel, which has a 100k rows limit, to achieve this, and the recommended alternative is via an environment Copy, or a 3rd party tool.

Benefits:

- Simplifies the migration process for individual entities

- Ensures consistency and accuracy across different environments

- Reduces the time and effort required to learn the 3rd party tool

Use Case:

This feature would be particularly useful in scenarios where specific entities need to be migrated or moved to a separate testing environment without affecting the entire organization. It would greatly enhance the flexibility and efficiency of entity management, enabling seamless transitions and consistency.

Thank you for considering this request. I believe it would be a valuable addition to the platform and greatly benefit users.

We are currently facing runtime errors following the upgrade of our .NET Framework class library from XrmTooling.CoreAssembly to PowerPlatform.Dataverse.Client. While the library compiles successfully, executing text template files that depend on this library results in runtime issues specifically related to Microsoft.Extensions.DependencyInjection.Abstractions.

This issue was not present with XrmTooling.CoreAssembly, where the text template files executed without any errors and returned the required objects as expected.

Current Impact:

Dependency Conflicts: We are experiencing conflicts during runtime due to incompatible dependency versions.

Failed Outputs: The text template files are failing to generate the expected outputs, hindering our progress.

Proposed Resolution:

Ensure Compatibility: Verify the compatibility between the PowerPlatform.Dataverse.Client library and the text template files to prevent similar issues in the future.

Your attention to this matter is appreciated, and we look forward to any insights or suggestions on resolving these issues.

Enabling quick create allows us to see the create form on right side panel staying on the same page where we can see Parent Entity record details. It can be N number of entities where we might be using quick create functionality. It’s a good feature.

But it’s also allowing user to create directly from the Application Ribbon (global buttons) by default.

Which can generate issues like:

1.     Can end up showing N number of entities in the List, which is unnecessary, can not let us have clean UI.

2.     For some scenario, where Lookup is getting value by from sub grid context and hidden on form, addition of new record from Top Application Ribbon will create an orphan child record.

This should be configurable that what entities we want to allow to utilise the quick create from the Application Ribbon.

For example, as in the entity property itself should be a flag field which can be On/Off just like enabling Quick Create feature for the entity.

tags: Dataverse, Application Ribbon, Global Buttons, Quick Create Menu, Entity, Hide, Show, Enable, Disable, On, Off

Many organizations rely on external experts or partner companies to help manage and optimize their Power Platform environments. Currently, guest users in an Entra ID tenant can switch tenants and access (existing) Power Platform environments. Guest users cannot (yet) access the Power Platform Admin Center, which is necessary to manage environments. This restriction leads to a need for having (additional) member users with seperate licenses assigned, resulting in unnecessary costs for customers, as well as inefficiencies due to needing seperate identities for different customers.

I suggest that administrative capabilities can be enabled for guest users within the Power Platform Admin Center.

It would be useful if we can have JavaScript function to make the form read-only. Currently there is no way to make a form read-only as a work around, we have to disable each fields in the form.

Hi All,

There should be a functionality or a report which identifies and ties together group of environments (typically Dev, UAT and Production) in most scenarios and have a report where it shows the following -

1. Which components are present in an environment and not in other environment(s).

For someone who's not using Power Platform and still deploying solutions manually, they usually see the issues while importing into the other environment. Today, it's at a solution level pertaining to components in the solution itself and not organization wide.

Hope this idea helps!

Thanks in advance.

Current Behaviour: Once the Azure Synapse Link for Dataverse is setup, all the tables with parent child relationships are synced with the correct value of Parent Name column in Child Table. However, when the parent record primary name field is updated in Dataverse, there is no trigger in Dataverse for child table, hence the parent table gets updated in Azure Data Lake and child table doesn't get cascaded with the parent's primary name field value. Any new child record created in Dataverse then has the new parent's primary name value. This leads to a discrepancy in the parent's primary name value in the parent table with respect to an old value in Child table.

ISSUE: Now it you have a reporting based on parent's name value from child table without knowing that the value won't be update, it leads to all the reports not functioning properly.

ASK: Please help with finding a way to have this data sync appropriately based on the changes in parent name. Alternatively, please help develop a tool which should update all the child tables with the latest parent's primary field name value