Power Platform Governance and Administration

When creating virtual tables using an SQL connection to the Serverless SQL Pool in Azure Synapse, there is a bug related to the primary key.

The table is created in Dataverse and includes a unique GUID and a primary field.

Retrieving multiple records works fine.

There is APIM bug when a specific record is selected.

Please make the Solution visible only to the solution creator in Power Apps makes the solution more secure.

When a new App or Flow is added to the solution, it becomes visible to everyone (makers) who has (System Customizer and Environment Maker roles).

The Flow run history is exposed to all the makers for 28 days period which is causing GDPR concerns over the visibility of Personal Data in the flow run and this is raising a few other concerns.

Also, a solution can be deleted by anyone. This is causing more issues and fears to Maker about his solution. Please can solution deletion be made only possible to Admins and Makers and make solutions more secure?

We are trying to achieve an efficient ALM process.

As per the title, we believe it is somewhat of a liberty to be asked to pay for capacity we did not create / use.

Specifically: I have created a brand new Organisation in my Tenant and went as far as to buy an extra 1GB Capacity add-on for it.

However, before I have even built anything, I am getting messages saying I am out of Capacity and need to acquire more.

The reason is simple: Dataverse Optimisation has moved these tables into File Strorage:

1. WebResourceBase (0.5 GB)
2. RibbonClientMetadataBase (0.5 GB)
3. Solution table (0.1 GB)

I am paying for a Licence to gain access to DataVerse already, and am willing to pay extra for Storage capacity for _MY_ data and file storage... But paying you for the above base-solutions capacity seems a bit like paying twice for the same service.

The idea therefore is to exclude the first-party system Web Resources, Ribbon and App data and Solutions from my Capacity count.

Currently, it is only available to configure auditing settings per org/environment/etc. These settings should be available to be tenant-wide for tenants with large deployments of Dataverse.

When performing Azure B2C authentication in Power Apps portal, if certain values are set to blank values in Azure B2C, they will not be mapped in Power Apps portal. 

If there are blank values, there will be value discrepancies between Power Apps Portal and Azure B2C. 

Therefore, we request that the function be improved so that blank values are also mapped. 

It would be useful to have a notice/warning when end users are deploying an app/solution that would subsequently create a Dataverse for Teams environment. This way end users' awareness of the environment increases, and notifications sent out for an environment they may have provisioned based on an app/solution they were testing/using in Teams, are a lot clearer for users when they receive the notifications.

This can be when the app/solutions are being installed/used, or even on the notification emails sent for Dataverse for Teams environments.

Overview documentation on what the Dataverse for Teams environments are, and how to manage them if they are Team owners.

Like these articles:

About the Microsoft Dataverse for Teams environment - Power Platform | Microsoft Learn

Automatic cleanup of inactive environments - Power Platform | Microsoft Learn

We recently raised an issue with Microsoft because users were reporting when using the global search, they could search exact matches by using inverted commas "Example" etc and this would bring back any records that have an exact match.

However when searching something like "C & W Fencing" this was matching on the word 'Fencing' and not the full string.

MS have advised this is expected behaviour - see comments below. Would be great if there was a way to find exact matches for queries like this.

We have some feedback from our Product Group informing that the behavior is the expected one:

Behavior1: The returned query results of any query mentioned below {query} is a combination of recall from ACS {###ByPassRankers=True###query} and suggestion cache {query}. On suggestion side, there will be no more than 6 records merged.

Behavior2: Relevance search cannot handle single character term well. This includes variations that contains AND operator between terms.

Details: When users are leveraging AND operator for search, no matter how they use this operator between search terms, we treat it as a strong signal to bypass BizQA query preprocessing and directly send it to ACS to get result to ask for exact match of those terms. As mentioned in below thread, relevance search (ACS) does not work well with single character terms, and will have difficulty finding target records. Its behavior will also behave differently (in a not satisfiable way) depending on how user add the AND operator between terms.

Example 1 {###ByPassRankers=True### C +& +W +Fencing} returns no result demonstrate that relevance search finds no result that satisfy the AND operator requirement. However, {C +& +W +Fencing} shows result because the records recalled are a combination of relevance search result (empty) and suggestion cache. Suggestion is based on different mechanisms thus behaves differently, this is a scenario that demonstrates why we leverage it as an advantage to improve recall rate.

Example 2 {C +& +W Fencing} and {C +& +W +Fencing} behaves differently because ACS recall behaves differently. In other words, {###ByPassRankers=True###C +& +W Fencing} and {###ByPassRankers=True###C +& +W +Fencing} behaves differently where the later one returns more records that includes term "Fencing". BizQA later merge the ACS recall with suggestion results and then ranking to get final display that contains more target records. For example, the record "Emma C & W Fencing Ltd" is the one merged from ACS recall.

As market is trending and moving at a fast pace, it would be a good opportunity of having the ability to perform Blue/Green deployment in Dynamics 365 CRM. It will help teams to reach zero downtime deployments and cause minimal/no interruption to business

I think that it would be really helpful if there was the possibility to easily export Cases in pdf: for now, it is possible to export Sales entities and personnalized entities in pdf, but there is no workaround to do the same with cases, you have to export them in a Word template and then export it in pdf.

So it would be great to add Cases to exportable entities.

In a model-driven app it is possible to specify for option-sets / choices, colors for the different options. E.g. Color 'Green' for 'Positive' Choice and color 'Red' for 'Negative' Choice.

This color configuration is not displayed for the field / column in the model-driven app.

The documentation also describes how colors can be set for different options in a choice set.

Nevertheless, there is only one color for all options: green regardless of the specified colors in the settings.