Dynamics 365 Sales

Currently out of box, when lead is qualified and a contact/account is created, system manages "Originating Lead" column on contacts & account and prefill this with lead that just got qualified. This field is used for rolling up activities on lead to show up in Contact's timeline. But this works only for new lead getting qualified that results in new contact creation.

If we qualify another lead to an existing contact, this lead is not captured in Originating Lead lookup column. To my knowledge this is a root cause for allowing system to show lead activities on contact timeline and since originating lead only looks for first time lead, only first lead's activities gets rolled up but not other leads who are still connected to same contact.

Possible Changes :

1. In my view, if we change behavior for Originating Lead column to keep appending more leads based on how many gets qualified to existing contact, we can use and maintain this mapping.
2. Timeline Control - There could be some behavior change in timeline to look for multiple leads that would get captured in Originating Lead field and show activities from them on Contact and account timelines.

The order of the filtering options should consistent as much as possible. Filtering options for column types Lookup and Choice are ordered the same way. String type has different order starting from the third line.

https://prnt.sc/4nobatScs2F7

Benefits: better experience, easier navigation, consistent design.

It applies to all Dynamics 365 products and Power Apps.

This hierarchy feature is going to deprecate by April - 2025 but this feature is very important for our clients, it would be really get if there will be a feature which replaces it or it would be really great if this feature is not deprecated at all.

We would like to implement plugin packages on all of our plugins, but the capability is missing on on-premises server. Our product has been around since Dynamics 2011 and it was developed onprem from the start. We have some big customers that still remain onprem and a lot of smaller customers have moved to online. We understand that the plugin packages are an important step ahead in the future since ILMerge has long been deprecated and Microsoft support does deny a support ticket if it's related to a plugin and ILMerge is involved. However, we cannot afford to maintain create two different products for onprem and online to fix this issue only.

The lack of plugin packages for on-premise potentially exposes the customers to legacy applications that have known security issues. For example, the BouncyCastle NuGet package version 1.8.9 is marked in Visual Studio as containing vulnerabilities. However, if I upgrade it to the latest package, the resulting ILMerge assembly is too large to be uploaded into CRM, and the deployment fails. As a result, the customer remains with this old package. Furthermore, ILMerge itself was developed with .NET 4.5.2, which has been deprecated as well. It's important to understand that even though on-premises customers are few in number, they are generally very large organizations and thus cannot be ignored. I therefore, urge the product team to look into introducing plugin package capability to the current CRM 9.1 version of on-premises as soon as possible.

To facilitate GDPR or PDPA (Personal Data Protection Act in Singapore), Ideal scenario:

For Sandbox or non-production environments,

1. PII fields* should be anonymized, if they cannot be cleared, despite whether user records are manual or auto-sync-ed from AAD (which is a is a product design).
2. This should be automatic with a configurable setting.
3. With the above achieved, users/developers/customizers/admnistrators should still be able to login to Sandbox environments with their usual AAD accounts for UAT/customization/development/etc work. E.g. a Tester login to the system to test and create email activities.

For production environments,

1. PII fields* of disabled/inactive users should be anonymized, if they cannot be cleared, despite whether user records are manual or auto-sync-ed from AAD (which is a is a product design).
2. This should be automatic with a configurable settings.

* E.g. these fields: username, email addresses, phones

Currently, as the URL below says, environment to environment migration for Word or Excel templates isn't currently supported.

URL: https://learn.microsoft.com/en-us/power-platform/admin/using-word-templates-dynamics-365#download-the-template

Sometimes, environments migrations are useful when using same templates.

It would be great if environment to environment migration for Word or Excel templates would be supported.

I'd suggest to be able (as it was in the past) to Postpone or Schedule the Wave updates for CRM.

This is possible for other products like Busienss Central already

The idea is to add possibility to sort on Sales Line via button on column in Swiss location, as it is available in other locations.