-
Maintain the value in the Search box between screens in make.powerapps.com
Suggested by Dean Holmes – New – 0 Comments
When putting in a search for Cloudflows or tables, etc. and then going into the flow, when the UI returns to the list, keep the value in the Search box, so we don't have to re-enter it all the time.
It is especially annoying when looking through a list of flows based on the name of the flow
-
Add custom columns to Activity table
Suggested by Humzah Kindi – New – 0 Comments
Currently we don't have any option to add column to activity table. It would be nice to have that. Like in case of our requirement we wanted to have business area column available on all activity types and filter all activities based on that in consolidated view.
-
Ability to stop moving forward in CRM Business Process
Suggested by Humzah Kindi – New – 0 Comments
We need the ability to stay in the workflow step if a condition is not met. Currently we need to write custom JavaScript to do that.
MS recommendations to stop navigation to the next stage. Below links are MS recommendations.
This one prevent saving data:
preventDefault (Client API reference) in model-driven apps - Power Apps | Microsoft Docs
-
editable grid to be available OFFLINE
Suggested by Anton Nyrkov – New – 0 Comments
IT will be great if editable grid to be available in OFFLINE for Model Driven app. Currently this not supported to work in OFFLINE MODE as this would render as READ-ONLY grid.
-
Limit access to model-driven apps (especially default app)
Suggested by Tony Bowes – New – 0 Comments
When general access to data is tailored through a Canvas App that uses Dataverse for data storage, users are still able to access the model-driven environment by the default app (D365Default). Could we have an option per security role that limits access to model-driven apps by any means?
NOTE: There is an option to limit model-driven apps, but it only impacts the discovery of model-driven apps, not access via direct link. Extending this feature to bar entry via URL would also be acceptable.
Additional discussions: Solved: Limit access to Model-driven app - Power Platform Community (microsoft.com)
-
Deleted lines between sections
Suggested by Rafal Piotr Laczek – New – 0 Comments
In last Release View 2 MS has deleted lines between sections.
Our users say that it makes layout much less user friendly.
-
Default SharePoint Document Locations
Suggested by 詩有人 西川 – New – 1 Comments
I would like to be able to specify a default Document Location when multiple Document Locations exist for a record.
Security requirements require that Document Locations be separated, but if the default Document Location cannot be specified, it is meaningless and may lead to user error.
-
Include Import from Exchange button in CRM
Suggested by Rakshanda Shinganagudi – New – 0 Comments
"Import from Exchange" button which is visible when we click on import from Excel button on Ribbon of entities like "Account" " Contact" etc but currently it is not supported to use.
Kindly make this feature available, it will help users to import data easily from exchange.
-
Allow Columns from the Many side of a Many to One Relationship in Views
Suggested by Hannah Rubin-Burrasca – New – 0 Comments
This is specific to an example from a third party solution called Anthology Reach. The goal is to display Applications(Entity) with Decisions(Entity) based on a specific Academic Period(Entity). They wanted to include Fields from both the Contact and Decision Entity in their column headers. There does not seem to be a way to drill down across relationships to add all of the below desired columns into one View regardless of whether the Base Entity is selected as Contact, Application, or Decision. Columns desired: External Identifier (Contact), Application Name(Application), Application Submitted (Application) , Decision Status (Decision), Review Status (Application). The desired output can be done in a Report. The columns available for selection in a View do not allow Decision related columns to be added to the header due to the M:1 Relationship between Decision and Application. The customer is aware this would create duplicate rows to be returned per Contact when creating a View with Application as the Base Entity due to multiple Decisions existing for each Application. They want the data to be returned like this.
-
Pin Solution
Suggested by NARENDRA MAGARE – New – 0 Comments
If there are 100+ solutions present in dev environment (Different Add-ins and accelerators installed). Every time dev has to scroll down or search for specific solution, he/she is working on.
Instead, if he/she can pin and it always shown on top, that will save time (and traffic). Generally, devs work on few selected solutions frequently, those he/she should be able to pin at top.