-
Option to use wildcard or not in lookup field.
In lookup field, when we search for the middle words, we have to include wildcards (*) to do so. However, not all users know this trick, hence, it is not user friendly. If we do not include wildcards, lookup field will only show all the results which start with the searched word.
Hence, in my opinion, there must be a configuration with each lookup field for the admin that whether it should use wildcard or not. If admin selects that it should use wildcard then it must allow the admin to configure a message which must be displayed below the control about how to use the wildcard.
If admin does not select to use wildcard, when users type searching words, the results will show both string which starts with the searched words and string which has the searched word in middle/ end of it. In short, it will be the same as using advanced search with include condition.
-
If Dynamics or any other Microsoft services detect any outage from Microsoft, the system should link the outage page (where we encounter any error message) which had a link to azure health status or Microsoft Service health.
Hi Product group team,
If Dynamics or any other Microsoft services detect any outage from Microsoft, the system should link the outage page (where we encounter any error message) which had a link to azure health status or Microsoft Service health. This would have saved us time reviewing our network connections, capacity, or any other environmental factor before we would engage Microsoft.
Thank you.
-
There should be a security role which allows user to access all flows in an environment without sharing
Normally, only admins can go to Power Platform admin center to access all flows in an environment. However, there are scenarios which users need to handle all the flows. It is not feasible for system admin to share all flows and monitor new flows if there are too many flows in the environment.
Hence, there should be a security role which allows assigned user to have full access to flows in an environment without having to share the flows.
-
User should be able to change the column label from number of week to actual date
In a chart, when we group the date by week, it shows week x of (year) but it is hard for user to track using the date. User should have option to change the column label from week x of (year) to actual date for easier tracking.
This is a needed feature and has been repeatedly asked in the community for a long time.
For example: crmchartguy.wordpress.com/2016/09/07/custom-date-formats-in-charts-in-ms-dynamics-crm/
-
Function to prevent users to change Tracking email settings
In Personalization Settings, user can go to Email tab and change the Tracking for their emails. Some organization already set the Tracking method for their users and do not want their user to change it. It will be great if admin can have a setting which prevent user from Set Tracking email in Personalization Settings