Wakako Watanabe

This request is related to the following Microsoft Ideas:

https://experience.dynamics.com/ideas/idea/?ideaid=0aee580c-9fe5-ea11-bf21-0003ff689146

The current feature does not support customized controls within BPF flyouts through the designer experience.

Therefore, customization of Field Properties is not reflected in the BPF.

Examples:

- Control Formatting" for Two option field

- "Default view" for the Lookup field 

If Field Properties is customized, it will display differently depending on whether the field is placed on the Form or on the BPF.The current behavior risks confusing users while using Dynamics 365.

We want the fields on the BPF to be displayed in the same as Field Properties in Form Designer .

Currently, there is no feature to control "Close as won" or "Close as lost" for Opportunity entity.

However, sometimes we want only certain users to perform these close process.

If "Close as won" and "Close as lost" could be controlled by security roles etc, the range of Opportunity operations would expand and Dynamics 365 would become more convenient.

Currently, we can use Duplicate Detection Rule to display a pop-up message when a field has duplicate records.

However, the message does not indicate which field is a duplicate.

We can identify the field by comparing it to the duplicate record or by checking the Duplicate Detection Rule, but this method is not efficient.

If the feature to display a message on the field of duplicate records when the record is saved is implemented, users would be able to correct the record immediately.

Dynamics 365 will be more convenient and our operations will be more efficient.

*This Ideas is based on the following Ideas.

https://experience.dynamics.com/ideas/idea/?ideaid=d1f472dd-0056-e911-b047-0003ff68dc9a

Currently, the default behavior is that the MultiSelect Option Set field cannot be used in Business Rule, Workflow or BPF.

https://docs.microsoft.com/en-us/power-apps/maker/data-platform/types-of-fields

However, we sometimes want to use MultiSelect Option Set field in Business Rule, workflows, BPFs, etc. in Dynamics 365.

For example, the following Business Rule: 

- Trigger : User selects "Yes" in the option set field.

- Action : Change MultiSelect Option Set field to a required field.

We think this default behavior is inconvenient and narrows the Dynamics 365 operation.

If this feature implemented, we will be able to use Dynamics 365 more conveniently.

Currently, notes created in the Lead entity are only carried over to the Opportunity enntity to which they are converted.

Notes of the Lead entity are not carried over to the Contact entity record created when converting from Lead entity to Opportunity entity.

If notes are inherited to the Contact entity associated with the conversion destination Opportunity entity, it is more convenient to check the contents of notes without opening the Opportunity entity record each time.

Currently, when fields set in BPF are updated in the canvas app, the BPF stage in the model-driven app is not moved.

If we want to advance the BPF stage, we need to move to the model-driven app and perform the operation.

The current functionality is inefficient in operations where the canvas app and model-driven app are used together.

If this feature implemented, we can use Dynamics 365 and Power Apps more conveniently.

"Show the label of this tab on the Dashboard" in the properties of a tab or section of the Dashboard is a feature that was enabled in the Web UI.

The current UCI does not support "Show the label of this tab on the Dashboard."

However, it still appears on the properties, so some users misinterpret the following.

- There is an issue where the label name is not displayed on the dashboard even though "Show the label of this tab on the Dashboard" is checked.

The current display is very confusing and may continue to cause confusion for users in the future.

Please consider to hide the display as soon as possible.

Currently, when we use the "Send Inviation" workflow to send an email invitation, we enter the URL of the portal for that environment in the body of the email ourselves.

However, this method is inefficient when managing multiple portals in multiple environments.

Because the following steps are required for each environment.

1 Confirm the portal URL for the environment

2 Open the workflow "Send Inviation" and enter the portal URL in the body of the email.

If a code like {invite PortalURL} to automatically retrieve the URL of the portal connected to that environment, we can use Dynamics 365 more efficiently and useful.

Currently, the default behavior is for Business Closures to be counted as Work Hours on tasks in the project entity record.

However, this behavior is very inconvenient for users.

Holidays are counted as Work Hours despite Business Closures, which prevents the correct calculation of Work Hours.

It is possible to make a resource a non-work day by assigning it a "vacation" in the "Work Hours" of a bookable resource, but I don't think this is a useful workaround since the task is assigned.

By applying Business Closures even on tasks in the project entity record, users can make more convenient and effective use of Project Operations.

Currently, it is possible to edit records of locked columns in Dynamics 365 by Excel import.

This is because the client (Dynamics 365) logic does not apply to Excel.

However, from an end-user's perspective, it seems strange that locked columns can be edited via import.

We think that if this feature is implemented, end users will be able to use Dynamics 365 more comfortably.