Power Platform Governance and Administration

Current Behaviour:

When an environment becomes enabled for pay-as-you-go and is linked to an Azure subscription, it stops consuming storage from the tenant-wide Dataverse storage pool. Instead, its consumption is billed to Azure. In pay-as-you-go environments, the first 1 GB of Dataverse database storage and 1 GB of file storage capacity aren't billed to Azure. However, any log storage capacity is immediately be billed. Log storage capacity is only used if you decide to turn on auditing for an environment.

Recommendation:

One of the main factors for wanting our production environment set to PAYG is to take advantage of the cost savings proposition of the power pages PAYG model for monthly authorized logins. This benefit is negated by the additional data storage costs incurred in the PAYG environment. We are being charged for the full capacity of our produciton environment, less 1GB, despite having over 15GB in available capacity just sitting there not being used in our tenant-wide capacity pool.

I think that being able to consume capacity from the tenant-wide pool prior to PAYG charges being applied would better align with the PAYG value proposition and would benefit businesses wanting to leverage the benefits of the new power pages licensing options.

There is a design issue in the activity entity. The filter for the number of days on the activity won't take in consideration the modification that was just did unless you manually update the page. The problem is anoying for the teams working with those fields and views because the have to refresh after each modification the page.

After opening a ticket (MS 2308030040005931) it was deemed that, when clicking Related > Cases or Related > Activities within account and contact records, the 'associated' views cannot be defaulted to other useful views (such as 'All Activities' or "All Cases"). Having this ability will save seconds per instance, which adds up over time.

Find/create Automated way to enable the feature "Delete disabled users from power platform" in all the environments of an organization.

Is there a method to facilitate the dissemination of a Power Virtual Agents chatbot across diverse domains? For instance, I have developed a chatbot within the abc@gac.com domain, but I am looking to extend its accessibility to xyz.wela.com. Currently, it appears that this sharing functionality is not supported as per Microsoft's official support.

Add the ability to manage access to an 'Area' in an app.

When wanting to change fields on the case form header, users have to use the little downward facing arrow to perform the changes. This is perceived too many clicks and to long winded by our users and we would like to have a possibility to perform changes directly in the form header. Fields like status reasons are updated hundreds of times a day, and it would be a quick win to have these fields made editable right in the header.

We have set duplication detection rule on Incident entity.

If the duplication detection alert window is popped up after the user attempt to create or update an Incident record, the user might need to view an existing duplicated record from the grid in the alert window in order to decide what to do with the record that is being created or updated, but trying to open an existing record’s form shows a warning that opening the form, which means - navigating away from the record that is being created or updated, will result in data loss on that record.

The existing duplicated record in the duplication detection alert window should be opened in a new window, allowing the user to go back and work on the new/updated record, with out loosing data.

Bug needing addressed:

New Dataverse UI launched in August 2023 that mimics the Copilot views for building tables. When you navigate to make.powerapps.com > Tables > New Table > ‘Add columns and data’ you are redirected to a page ending in /createWizard#CreateTableFromBlank where you can create a new table and the primary column. When the Display name is updated, the Plural name updates automatically as in the prior UI. The Schema name (and related Logical name) buried under Advanced options are not getting automatically set (like they used to) to the entered Table Display name and are left as newtable#.

Please look into fixing this straightforward bug of copying text from Display name field to Schema name automatically that currently exists in other table creation screens!

Additional Information:

The Schema name can be manually updated in the new Create a Table From Blank screen under Advanced options which also sets the Logical name (to all lowercase), but with the inability to change these logical/schema names later without blowing away the entire table, this is an extremely poor functionality that will lead to problems in misspelling, case differences, or forgetting to update these from newtable# when this automated updating was there prior.

This automatic updating is still in the old UI if you navigate to make.powerapps.com > Tables > New Table > 'Set advanced properties'. Entering Display name here updates the Plural, Logical, and Schema names as expected and appears to have been missed functionality when planning the switch to the new table creation screens that mimic the Copilot automated table creation screens on /createWizard#CreateTableFromBlank.

When this bug was presented to Microsoft Support, they indicated this was "by design" but had no idea how or why this would be designed in such a way when it already exists in another location, then they sent us this Ideas/Feature Request link (to likely be ignored and go away), and that was the end of the Support Contact. Not exactly the most glowing customer support or development planning and implementation.

Currently, "Child Items Parent Id" property pulldown "Bind to a value on a field" in Power Apps Grid currently only supports Lookup fields with N:1 relationship.

However, depending on the operation, we want to use N:1 or N:N relationships.

Once this feature is implemented, we will be able to use Dynamics 365 and Power Apps more conveniently.