• 2

    Automatic record creation rules in the web client

    Suggested by Toya Nomura New  0 Comments

    Automatic record creation rules in the web client will be supported until April 1, 2023.


    In the meantime, if you try to create a new automatic record creation rule, you will receive an error, and to avoid it, there are too many steps to go from customizing the system to applying the "Create and Update Record Rule Items - UCI" setting.


    If there is an easy way to improve this, it will be easier for everyone to use and there will be no disruption until April 1, 2023


  • 10

    Return of the "Reply" button when responding to emails

    Suggested by Arturo Acosta New  1 Comments

    Following the release of the 2022 Wave 2 when responding to emails only the "Reply All" button is readily available. One has to click on a drop down menu to use the "Reply" option. We have 100s of D365 Teams integrated with shared event inboxes that we use to respond to customers all around the world in multiple languages. When using the "Reply All" button this causes several issues for us. One, it causes ticket loops since we currently have Automatic Reply enabled on our Modern ARCs. Two, it creates unnecessary emails send back to ourselves when not needed and increasing unnecessary storage. I would like to propose the return of the "Reply" button. At least in our case the "Reply" button is used more often than the "Reply All" and also it eliminates the extra steps needed to use the "Reply" option. Thanks kindly.


  • 1

    Classic App designer limitation

    Suggested by Vinay Akki New  0 Comments

    In the classic app designer where views and forms can show up as unchecked if you have more than 5000 views and forms in your environment. The currently advised mitigation is to use the Modern App Designer (make.powerapps.com) if it is available to you.


    Please help in creating all the views available for the customers to check and not to limit the number of views for the classic view.


  • 1

    Enable session inactivity timeout for Canvas Applications

    Suggested by Riyaan Brink New  0 Comments

    In the PowerApps admin center there are features to enable session expiration and inactivity timeouts. These are only enforced on Model-Driven Applications. To ensure we can provide better security, we require these features to be enforced for Canvas Applications as well.


  • 1

    Enable session inactivity timeout for Canvas Applications

    Suggested by Riyaan Brink New  0 Comments

    In the Admin center there are features to enable session expirations and inactivity timeouts. These are however only enforced for Model-Driven apps. This is really needed to provide better security for canvas applications as well.




  • 1

    Tool to modify the author of the environment and the processes associated with it

    Suggested by Vito D'Ambrosio New  0 Comments

    Example:

    The CRM production environment was created using a user linked to a real user and not an admin user. In fact, by removing the license from the user who created the production environment, processes such as qualifying leads at opportunity did not work.


    Therefore, it would be convenient to have an automated tool that would allow us to change the name of the author of the environment and thus the owner of all processes and flows (including background flows) connected to the user who created the environment. 


    Thank you :)


  • 1

    Possibility to see detailed data usage per entity

    Suggested by Henrik Torsten Franzén New  0 Comments

    We're having issues finding exactly where we have a lot of data and we've been trying to delete certain data, mainly activities, for several entities.


    Exactly what we've been looking for is how much data is being used per activity type, since alot of data seems to be close activities. If we were able to extract this data through SQL or see it in dashboards AND if we would be able to act on this that would solve our problem. We've been in contact with MS support regarding this and they are sadly clueless with helping us with this, while they mentioned they had a script for this or similar but that doesn't work anymore.


  • 9

    Change the default view of user entities in bulk

    Suggested by Kazunori Mori New  0 Comments

    Currently, "Manage users in Dynamics 365" sets the default view of the user entity with a pin. However, because each user must change the default settings, it takes time to display the same view to all users.

    Being able to change default settings in bulk makes design easier for administrators. Therefore, if this feature is implemented, it will be very beneficial for users who use this app.


  • 4

    Upload State at attachment

    Suggested by Florian Sutter New  0 Comments

    While file Upload as an attachement no state is shown.

    If the File size is big and it needs some time - nothing happens.

    For the USer it seems like it is not working.

    After the file is again choosed and added suddenly it is twice in the attachement.

    An State like an loading bar or anything else should be shown and the file name is directly visible.


  • 2

    Control End-Users/Team Owners capability to raise a MS Support Case.

    Suggested by Julian Ferrer New  0 Comments

    End-users/Teams Owner of Teams Dataverse are able to raise support request without the knowledge of the Power Platform Admins. Admins do not have the visibility to track the active cases with Microsoft and do not have the visibility to the issue.

     

    -When an end-user is a Team Owner of a Teams Dataverse Environment. They automatically have the “System Administrator” role(since we have a large tenant the scale of Teams Dataverse is huge).

    -When an end-user has a Power BI Pro licensed assigned.


    Workarounds:

    ·       remove the user from being a Teams Owner

    ·       remove the Power BI Pro license.

    blocked the apps(PowerApps, Milestone, and etc.) in Teams that creates Teams Dataverse.


    It would be great to have a control in raising the support cases. A better workaround is to send notification or alerts to Power Platform Admins. It will help track tickets and support the users who are in need before they raise the Microsoft Case.