Power Platform Governance and Administration

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.

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.

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.

Issue -

Quick actions buttons have been configured per these articles https://learn.microsoft.com/en-us/power-apps/user/relevance-search#quick-actions 

For more information on how to configure quick actions, see https://learn.microsoft.com/en-us/power-platform/admin/configure-relevance-search-organization#configure-quick-actions-that-appear-with-dataverse-search-in-model-driven-apps  

OOB buttons show up fine both on search quick action & grid however custom button(any) are not showing up neither on Data Verse search quick action nor on grid. We have validated that this custom button shows up on home grid. 

Exact Repro Steps: On Data verse search, search for any account record, it will render matching records that will have quick actions associated on quick action menu & grid. 

We have tried with all 3 enable rules however they don't work for custom buttons -

ShowOnQuickAction 

ShowOnGridAndQuickAction 

ShowOnGrid 

We followed steps documented in our article https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/command-designer-overview#command-bar-locations it seems that quick action buttons can be added or edited using new command designer however no luck(we don't see custom buttons showing up in quick action/search grid). We tried changing the order of the custom button , existing buttons were having 40,50 & 61 sequence numbers and we gave 45 for new custom button. Still we were not able to see the custom button.

Tools Used - Ribbon Workbench & new command designer.

References - Customize the command bar - Power Apps | Microsoft Learn

Ask - Can we have these ability to add custom quick actions button on DV search/in future versions/releases, this will enhance search experience for customer end users.

Currently there is no power apps connector add in available for excel in mac os. This is mainly used to update dataverse table data through excel. This is a very big limitation with company's stakeholders using mac books. This is an important feature and amazed that its not available for excel in mac os.

The ability to customise the message that is being sent to the internal users is not currently there. When the users get the current message, they are not able to appreciate or relate back to what they need to do. So, if the ability is provided to Power Platform admin, we can customise the message in a language familiar to the user community in the organisation.

Customer requirement - We are setting the PCF Grid in the Entity View which doesn’t have much property to make the modification. We need this Grid to be displayed only in certain views ( Active projects). We need the 'Filter By' option in the column header for the PCF Grid developed with same as OOB Filter Option. 

Currently, there is this enable filtering property that determines if filtering options are available to users in the grid column header dropdowns, it is ONLY available at Entity level.

https://learn.microsoft.com/en-us/power-apps/maker/model-driven-apps/the-power-apps-grid-control#configure-the-power-apps-grid-control 

Only display the Unified Support Agreement with the Service Hub User Identifier in LCS to select when opening a support ticket. LCS currently displays the 3 selections for agreement. 1. Unified Support Agreement with the Service Hub User Identifier 2. Unified Support Agreement without the Service Hub User Identifier 3. Regular support without Unified Support. We only need the first one to appear since the second is a duplicate, for creating a ticket purposes, and we would never select the third while we have a Unified Support Agreement. We have had instances in which someone creating an MS Support Ticket through LCS selected the third option and it went into the regular support queue, not the Unified Support queue for which we pay a lot of money. We were forced to close that ticket and open a new one in the correct queue since MS was unable/unwilling to move it into the correct queue for us. I requested this change through MS Support, but they were unable/unwilling to change this to improve the user experience. Would you please make this UX improvement when you move to Power Platform?