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.

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)

In last Release View 2 MS has deleted lines between sections.

Our users say that it makes layout much less user friendly.

"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.

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.

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.

The request is to allow the values of multi-select option set fields to be uploaded, using a csv file.

Currently it is possible to do this by upload an excel file and dividing the multiple values with the ";" symbol.

This cannot be achieved within a csv file.

Whenever you close any record in a workspace app, you always get the message:

'Close this session?

You will lose any unsaved changes in the session and won’t be able to return to it later.'

This message appears regardless of whether the record has been changed.

This is annoying for users.

Would be far better if the message only appears if the record has been changed.

We need to have access to the Power Platform Admin Center audit logs. Although I understand this is an admin interface, most Microsoft 365 product have audit logs for admin (tenant) activities - Azure, Exchange Online, SharePoint Online etc.

For example, using a Set-TenantSettings command does not generate an audit log. Also changing setting like "Who can create trial environments" in the "Power Platform settings" would not generate an audit event.

We require these audit logs for security and compliance reasons.

We are experiencing an issue where on the Dependency list it states an object is in use however when we check the form the view in this example is not used anywhere on the lookup field

We believe this is a cache issue and when I remove and readd the field to the form the issue dissapears and the system no longer thinks that object is a dependency.

Please provide a fix for this - I've also raised this with MS support who have suggested I log a new idea

 TrackingID#2207120050002053

Kind regards,

Sagar