Ideas site for PCF Gallery, submit here your idea for a new PCF control
Render a lookup as a dropdown (optionset)
Rendering a lookup as an dropdown/optionset would be for things like reference data (e.g. country lists). Users could add values without needing system customizer role and also you would be able to "retire" options.
Hierarchy control to replace deprecated control for model-driven apps
The hierarchy control in model-driven apps is being deprecated by April 2025.
A custom PCF control with flexibility to be used on standard and custom tables would be really useful for many organizations since Microsoft is not replacing this with a new universal control.
Hierarchy control in model-driven apps is deprecated
Effective October 2024, the hierarchy control, which is used to define and query hierarchically related data in model-driven apps, is deprecated. The control will continue to work in existing apps until April 2025, at which time it will be removed from the product.
The hierarchy control allows users to visualize relationships between records for a table. This is applicable for any table that has a self-referential relationship.
Why is this needed?
Due to low usage, issues with accessibility, and incompatibility with the modern look, the hierarchy control will no longer be supported.
Impact
After its removal, end users will not be able to view the visual representation of the hierarchical relationships of records.
Action required by you
You can enable the control until its removed in the product by editing the app settings. Go to Power Apps (make.powerapps.com) and open the app you want for editing. Then go to Settings > Features tab and enable the Enable the "View hierarchy" capability setting.
If the hierarchy view is essential to your app, a custom PCF control that handles the hierarchy view must be created and deployed.
Dynamic sub-grid with contextual awareness using FetchXML
A great feature of the Common Data Service (current environment) List Records action in Power Automate is that you can use dynamic FetchXML queries. E.g. you can create a FetchXML query and use variables to dynamically update the query in the context of the flow:
It would be great to have a similar feature for sub-grids on forms. E.g. the Account form it would be nice to be able to show hierarchically related opportunities in the context of the selected Account.
Jonas Rapp has a method where a plugin is used to achieve that. I have absolutely no idea if this is even possible to achieve using PCF but it would great if it is.
Full file explorer connected to Sharepoint
A control like : https://demos.telerik.com/aspnet-ajax/fileexplorer/examples/overview/defaultcs.aspx
That uses Sharepoint as a backend (for instance, use it in Dynamics for Sales).
Gant chart control
Looking for a control that work like MS project/ gant chart. with drag/drop, task sequencing and similar feature. This will help the canvas app developer to develop a light-weight task management application.
Organization Hierarchy Chart in PCF
Hello Team,
We are looking for the Organization Chart which looks same as we have in Dynamics 365.
Below is the overall hierarchy which we are trying to achieve. Please if you guys can develop it would be great for us.
Project Plan
Similar to https://pcfgallery.userecho.com/en/communities/1/topics/9-subgrid-with-re-ordering-of-child-records, but add also children in a hierarchical/tree view, such as in Microsoft Project. For model-driven apps.
Power Automate Approvals to Canvas apps
It would be nice if we could embed Power Automate approvals to canvas apps directly. Now we can only get a link that takes user to the approval center. Our users complain that it's diffcult to approve from another browser tab/window and then come back to the app.
PCF button or control to trigger the on select flow.
PCF button or control to trigger the on select flow.
Control Duration fields (Whole Number field with a Format=Duration) to present in either Hours or Minutes
Currently, duration fields will present inconsistently in either minutes or fractions of hours. Screenshots below show how the same field with the same value is presented differently across different forms and views.
I have heard that the logic is to convert in hours as long as you use 15 minutes steps, but in my example that is clearly not the case. And even if it did, a consistent presentation regardless of the duration is desired. With Duration fields being used heavily in D365 Field Service, this is very confusing to users.
The ask here is to provide a control that would allow a global setting to either present in hours or minutes. Or possibly to have one control that presents in minutes and another that presents in hours.
Customer support service by UserEcho