Power Platform Governance and Administration

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

Put back the ability to 'view more' and 'view less' functions at the top of an email in the timeline. This functionality was removed in the 2022 Wave 2 update. Users do not need to scroll to the bottom of a 5 page email to 'view less' when the most recent information in an email thread is at the top.

The option to copy or clone an Power Platform environment with just its Dataverse database incl. all the data, but without all the Power Apps, Flows etc. would be a very helpful feature for data migrations.

Currently only a copy of the whole environment incl. everything or the customizations and schemas only is possible.

Expand the current reports on Power Pages authenticated users and anonymous users with the following info.

Providing admins with better insights wether the numbers shown in the report are correct and that they know where those numbers actually come from.

Authenticated users:

• Contact GUIDs
• date and time on which the contact logged in

Anonymous users:

• IP address or some other identifier on which an anonymous user is registered.

Currently, when “Enable editing for Power Apps grid control” is set to “Yes”, changes made to a multi-select choice column are not saved until another field within the same record is modified.

From the user’s perspective, this behavior appears as if the input has not been applied, which could lead to input errors or data inconsistencies in business operations.

In light of this, we request an improvement so that changes to checkboxes in multi-select choice columns are saved immediately upon modification.

The customer strongly expects this behavior to be improved to enhance user experience and input accuracy.

We kindly ask for your consideration.

-> To provide "number of records" info for the CRM tables in the "Resources > Capacity" tab.

Background:

• Now we only having "table size" info in the "Resources > Capacity" tab.
• We were having a custom module's table that having 75 million records, which from the "Resource > Capacity" tab, it was showing 80GB++ table size.
• We started doing the "Bulk Delete", and after removing 1 million records, we can see the table size reduced to 67GB.
• We continued the "Bulk Delete", and after 3 weeks of continuous "Bulk delete", the table left 11GB, but the size static as 60GB. This triggered us the doubt on the accuracy of the database sizing info, we are being charged by "database sizing volume" per month.
• If we have the "number of records" info available in the "Resource > Capacity", then we can calculate the size of 1 record for each table, so that we can counter check the accuracy of the "table size", and ask Microsoft team to check if there is any dispute on the table sizing,

Thanks.

In the PPAC, when going to resources > flows for a large environment, not all flows are displayed. Please fix this so admins can easily reassign flows when needed rather than having to go through powershell.

Reference: TrackingID#2504070040013814

https://learn.microsoft.com/en-us/troubleshoot/power-platform/power-automate/flow-management/manage-orphan-flow-when-owner-leaves-org#assign-new-co-owners-to-an-orphaned-flow

It is not "hard" to find orphaned flows, it is currently not possible.

This suggestion revolves around the automatic lookup "name" field resolution. I'm posting it under "customer service", but it's really about the broader Dynamics 365 CRM system logic.

How the platform works:

-----------------------

Every time an entity is opened (i.e. 'Retrieve' operation) or when multiple records are searched (view, advanced find, etc. i.e., 'RetrieveMultiple' operation) all the lookup names are resolved again. Even though in the CRM DB there are columns for both the lookup record id and name, the platform will always resolve those lookup names again.

This is understandable as the name may have changed in the interim, so it would be appropriate to show the latest information to the user rather than show them the old value that was populated when the parent record was saved. This is really useful as I've used this behavior multiple times when I wanted to translate lookup names for multilingual environments where each user wanted to see the values in their own language by creating the necessary retrieve and retrievemultiple plugins.

Issue Description:

------------------

Quite often the primary name of some configuration entities will really never change or very rarely change. Having an extra retrieve operation for those entities is an overkill that simply takes extra processing time and makes the user experience much slower. The worst part though, is when those lookups point to virtual entities. Each time they are resolved this is a call to another system to fetch their latest name. I have retail customers that have 5-10 lookups on the case and phone call entities in order to link the case to the ERP records the case is for. Each time the case is reasssigned or during resolution or even when an irrelevant field is updated, those lookups are again getting resolved resulting in extremely slow system response times for the end user. The names of those entities are really the order number, order line number, loan number, coupon number, etc. Names that are really impossible to change, yet they have to get resolved again on every operation on the parent entity. If all of them are populated that's 10 calls to an external system to get the data. Not to mention that if you add them in a view then that's 25-250 records that need to get resolved so that's another call to the external system.

Suggested Improvement:

----------------------

The ideal way to address this would be to have the automatic lookup name resolution on the entity level as a configuration. Just another checkbox to configure the desired behavior per entity. For entities were the implementer knows this is fixed data that never changes they can elect to turn this off and speed up the system. This doesn't need to be done only for virtual entities, it can be done for all entities in CRM. This would be the best way to address it. That way the issue for never changing lookup resolution can be addressed, especially for customers that heavily use virtual entities.

I would take it one step further for rarely updated ones as well and if the automatic resolution is disabled for one entity, then at the level of the parent record form show an icon next to the lookup to update the latest name. Similar to the behavior of roll-up or calculated fields.

The system performance improvement for virtual entity lookups will be massive if this is done.

We strongly believe that the fact that the Finance and Operations Basic User role is only assigned when a user has a fully qualified Finance license is a mistake. As outlined in the Microsoft Learn documentation on Authentication and Authorization (https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/power-platform/authentication-and-authorization#security-model), this role is intended to provide access to Virtual Entities-a feature that is not limited to Finance-related functionality alone. Given this, the role should also be assigned to ALL users with a fully qualified FnO license (like project operations license, SCM license). We believe this is simply a design flaw or bug in the automatic role assignment process. Additionally, the same documentation only discusses the assignment of this role, not its revocation, which further adds to our concerns regarding the current behavior.

Customers are often choosing to use Project Operations licenses for their FnO operations, as this license is cheaper then a Finance license, and qualifies as a full FnO license according to the licensing guide of March 2025:

• on page 24: "Project Operations licenses have no roles at the Operations – Activity level, but full users of Project Operations have rights to Operations – Activity roles for other Dynamics 365 products, such as Finance and Supply Chain Management"
• on page 39: In the table of capacity licenses, you can see that the same capacity is foreseen in the Operations database for Commerce, Finance, Project Operations and SCM licenses.

It does not make any sense that rights to use virtual entities would not be applicable to the other fully qualified FnO licenses like project operations or supply chain management.