Yuya Takeshita (Japan Concentrix KK)

We have confirmed that the popup blocking setting is the cause of an event in which userprincipalname() cannot be retrieved correctly in the PowerBI workspace. 

It took us some time to remedy the problem because the Docs did not mention that the pop-up blocking settings prevented the updating of parameter values. 

That being said, I would like to propose that a statement be added somewhere in the document that pop-ups must be allowed, as I don't normally think that pop-ups interfere with the update process as it is running. 

We are aware of an event in the Power BI workspace where a parameter update failed due to a popup blocking setting. 

It took us a long time to remedy the problem because the public information did not mention that the pop-up blocking settings prevented the updating of parameter values. 

Since we do not expect pop-ups to interfere with the update process while it is running, we would like to see a statement added somewhere in the docs that pop-ups must be allowed. 

In Dynamics 365 Customer Voice, the current behavior is that uploaded files are saved to OneDrive by default.  

Although it is possible to specify the destination of the file using Power Automate, we would like to improve this so that the destination of uploaded files can be specified directly from the form properties or Dynamics365CustomerVoice settings without using other connectors. We would like to see improvements to this functionality. 

We are implementing an automatic update of Project Operations, but we would like to have a mechanism to detect and notify us of the failed status when an update has failed.  

Currently, the system checks for errors by discharging errors, but unless we check for errors voluntarily, we are unaware of the system and do not notice that an update has failed.  

If there is a conflict between automatic updates and the customer's release work, the latest status will not be reflected, which may affect business operations, so we would like a mechanism to be established to notify us. 

Currently, in the default environment, the role of environment creator is not authorized to delete model-driven apps. This is because only the Administrator role is configured to have delete privileges. However, since environment creators often create and use model-driven apps, it is desirable to give them delete privileges.

Since environment creators often create and use model-driven applications, it is desirable to allow them to delete them when necessary.

Also, by granting appropriate privileges outside of the administrator role, the burden on the administrator can be reduced and the environment creator can work freely.

For these reasons, we strongly request that the environment creator role be granted the authority to delete model-driven applications.

Currently, delete permissions for model-driven apps cannot be assigned to those created by individuals, and can only be assigned to all model-driven apps in the environment as "grant permission to delete" or "do not grant permission to delete " only.

Since there is no deletion authority for apps created by the user, the default environment is overrun with superfluous apps, and the system administrator must handle the deletion of it. 

To reduce the burden on the administrator, we recognize that the environment creator must have the authority to delete model-driven apps created by the environment creator, so we would like the scope of authority for security roles to be changed.

Currently, when a file upload question is created in a Customer Voice survey form, the file uploaded by the respondent is stored in the OneDrive of the user who created the form.

However, if the form creator leaves the organization, the uploaded files cannot be viewed or shared, and the form must be recreated.



Since it is complicated to send a notice to respondents that the URL of the form has been changed when the form is recreated, we would like a function that allows the survey to be saved to the OneDrive or other location owned by the user with whom the survey was shared.

When adding a member to a marketing list, it is currently impossible to add a member without searching one by one.

Currently, the marketing list is associated with many-to-many relationships, and when adding a member, there are only two options: "search and set one at a time" or "select multiple companies from the client company table and add them to the marketing list.

Please implement a function to add multiple companies at the same time.

When sharing a record from a custom table in Power Apps to Teams, currently only the link is shared by design.

The Opportunity table will show up to 5 items in the shared view, but the other tables and custom tables will not.

When a record is shared, users have to go to the trouble of opening the link to see the contents, which is inefficient for business.

We would like to see a function implemented so that not only the link is shared, but also the shared data is displayed on the chat.

We would like to have a field that allows us to see how many hours a task was planned for at the time of order receipt, and to see how much difference there was during and at the end of the project.

However, the Project Task Grid in Project Operations does not allow the addition of custom columns because it is the item used to manage the Work Breakdown Schematic (WBS) in iFrame, which is hosted within Microsoft Dataverse.

We would like the ability to add custom columns to achieve the desired behavior.