Dynamics 365 Sales

If the "Enhanced experience for adding products" is enabled and multiple products are added to a quote, the order in which the products were selected does not correspond to the order in which the products are created in the quote.

It would be desirable that the order in which the products are created in the quote corresponds exactly to the order in which the products were added in the enhanced experience.

This is important so that the sales representative is able to create the products in the exact order that the customer requested, and thus be able to build the quote according to the customer's wishes. 

We came to know that view Hierarchy button is going to be deprecated. Good number of customers use this to view the Account hierarchy so I believe it should not be deprecated

If Dynamics 365 Sales is integrated with Business Central and uses the multi company synchronization functionality, the company name from BC isn't visible by default on the opportunity form in D365 Sales.

Only an ID of the company is shown.

As a result, it is not clear to the sales person to which company the opportunity is synced.

Please re-enable the drill-through functionality that allows us to publish PowerBI reports and users interact with clicks.

Pre 10-March-2024 it was possible to drill through but a 'bug fix' removed this functionality

see support case 2403120050000245 

Currently, the functionality to change a component to another component is not implemented. If the relevant section is excluded from export, adding this feature would improve user convenience.

It would be useful to have a setting that would turn on Try the new look for all users in the environment at once, and automatically turn it on for users who turned it off and were using the old screen.

Currently there is no setting to turn it on for all users, so we are requesting a setting function to turn it on for all users.

Currently, there is no functionality implemented to change the owner of a model-driven app.

Implementing this functionality will allow users to properly manage model-driven apps even when the owner leaves the tenant.

After reviewing the behavior of the “Remove Format” button in the Dynamics 365 rich text editor, we have confirmed that its current design removes only inline-level formatting (such as "span", bold/italic, and inline font-size or font-family), while styles applied directly to block-level elements like "p" tags are not removed.

As a result, when font-family or related styles remain on "p" tags and the email is opened in Outlook, Outlook evaluates fonts on a paragraph-by-paragraph basis. This can cause inconsistent font rendering between paragraphs, even when the content is the same language (for example, Japanese).

While this behavior is understood to be by design, from a user perspective it can be confusing, as using “Remove Format” does not fully normalize the visual appearance.

It would be very helpful to have:

・An option to fully remove font-related information inside "p" tags when “Remove Format” is applied

This would help prevent font inconsistencies when composing emails.

When you upload the Quota file to your Forecast and you only filled out Quota (Direct), then the Total Quota values for the Parent records have to be calculated automatically.

But if you did fill out Quota (Parent) in the file, then there should be no automated calculation, it should take the values from the file.

When creating a new "Account" in Dynamics 365 Sales, if Dual Write is enabled for this entity, the record is synced to Dynamics 365 F&O as a "Customer". As in Dynamics 365 Sales, the Account entity does not enforce validations on Account Address fields, users can freely type whatever City, State, District, Zipcode, Country they wish. As these fields are enforced by Data Lookups on D365 F&O, if the user does not insert a valid field in Sales (valid = existing in F&O), the record creation fails, due to a data sync failure.

If a deployment of F&O and CE is expected in enterprise environments with harmonized and consistent data sync among such relevant entities, data lookups and validations should be enforced and enabled in CE when creating an Entity Address, so users are not disrupted while creating master data, and a recurrent customization is not required for every single deployment.

Thank you.