Kenny Tang (WICLOUD CORPORATION)

Currently, the Dataverse Recycle Bin retains deleted items for only 30 days. After this period, the data is permanently deleted.

For some users, data may be accidentally deleted due to errors in their code or workflows. For instance, a user might run a script that mistakenly deletes a large set of records because of a misconfigured filter. These users need time to correct these errors before restoring the data, and 30 days is often insufficient.

I propose extending the Recycle Bin storage period to 90 days. Alternatively, users should have the option to set a custom period for how long deleted data is stored before permanent deletion, similar to configuring audit settings.

When users hover their mouse over a task on the schedule board, a popup appears to display the task's details. While this feature can be helpful, some users find it frustrating as the popup can obstruct their view, making it difficult to reschedule tasks by dragging and dropping.

To enhance user experience, it would be advantageous to introduce an option to disable these hover popups entirely. This would empower users to manage their tasks more efficiently and provide the flexibility to choose whether or not to display the hover popup.

The data used for the Customer Service historical analytics reports are stored in a Microsoft-managed data lake. Some customers have expressed a desire to pull this data from the reports into their own databases, such as Excel files or their own data lakes.

Currently, there is no way to extract data directly from the reports, requiring users to manually enter the data into their databases. This process is time-consuming and prone to errors.

Introducing a feature that allows customers to access and export data from the reports would be highly beneficial. It would enable customers to efficiently use the data for their business needs, improving overall productivity and accuracy.

Dynamics 365 environments are typically updated every weekend. However, to ensure optimal performance and address critical issues, there are times when updates are rolled out mid-week. These updates are executed automatically, without prior notifications to users.

While this approach ensures that the system remains up to date, it can sometimes lead to confusion. Users might notice changes in application behavior, deprecated features, or even new functionalities without any prior warning.

To enhance user experience and minimize disruptions, it would be incredibly beneficial to provide notifications about the timing of these updates and the changes they bring. This proactive communication can help users prepare for the changes, adjust their systems accordingly, and effectively communicate with their teams. Additionally, it aids in troubleshooting any issues that may arise due to the updates, ensuring a smoother transition and continued productivity.

According to the Microsoft Learn documentation on Who Knows Whom (WKW), the enhanced WKW feature uses data directly from Exchange to identify and establish relationship connections. To enable this functionality, Server-Side Synchronization (SSS) must be properly configured.

Once WKW connections are established, all related emails are synchronized into Dynamics 365 and displayed in the timeline. However, not all emails may be relevant to business activities, and some may not need to be tracked within Dynamics 365.

To address this, it would be highly beneficial to provide users with the ability to configure which emails should be tracked in Dynamics 365 or excluded from the timeline—while still allowing the enhanced WKW feature to function effectively in the background.

In Dynamics 365 Sales, when using the "Percentage of List" pricing method for Price List Items, the system currently rounds the amount based on the Currency Precision setting. This behavior differs from other pricing methods, which use the Pricing Precision setting for rounding.

This inconsistency can be confusing for users, as it introduces a discrepancy in how prices are calculated depending on the method used. It may also affect users' ability to set accurate and consistent product pricing.

To enhance usability and ensure a more intuitive experience, it would be highly beneficial for all pricing methods to follow the same precision logic. Aligning them under the Pricing Precision setting would streamline the pricing process and empower users to manage product prices with greater confidence and clarity.

Currently, the Customer Service chat widget in Dynamics 365 offers limited flexibility—it can only be closed, minimized, or set to a fixed size. However, many clients would benefit from the ability to maximize the chat widget for improved visibility and user experience.

Unfortunately, there are no built-in settings to control maximization or minimization behavior. Users can only configure the widget’s dimensions, which restricts customization.

To achieve a maximizable chat experience, users must currently resort to developing a custom chat widget using code, which can prove to be challenging for those without web development expertise.

Related documentation: https://learn.microsoft.com/en-us/dynamics365/customer-service/develop/develop-live-chat-widget

Introducing a maximization setting in the Copilot Service Admin Center (CSAC) would empower users with greater control over the chat interface, enhance accessibility, and ultimately help organizations deliver more tailored and effective customer service experiences.

At present, there's a known limitation when using UTM tracking in email links that point to Dynamics 365 (D365) records. If tracking is applied for these links, recipients will encounter an error when attempting to open them after the email is sent.

This behavior has been confirmed by the development team as expected—UTM tracking is not supported for links that lead directly to D365 records.

However, there's growing interest among users to enable UTM tracking for these types of links. Doing so would provide valuable insights into how recipients interact with D365 records via email, enhancing visibility and engagement tracking.

Supporting UTM tracking for D365 record links would be a significant improvement, empowering users with better analytics and a more seamless experience.

In the Rich Text Editor (RTE) for the New Look in Model-driven apps, editing hyperlinks requires users to select the entire hyperlink text.

This was not the case with the legacy look, where users could simply place the cursor on the hyperlink and choose Edit link without selecting the full text.

This limitation can create a frustrating user experience, especially when the hyperlink is very long. Selecting the whole text takes extra time and effort.

If the RTE control in the new look allowed users to edit a hyperlink without selecting all the text, it would make the editor easier to use and improve the user experience.

Snowflake has announced the deprecation of username/password–based authentication as part of its security and MFA rollout, as described in the following blog: https://docs.snowflake.com/en/user-guide/security-mfa-rollout

As part of this change, Snowflake recommends using Key Pair authentication for service and application connections, as it provides stronger security. This authentication method is already supported in Power BI, but it is not currently available in Microsoft Sustainability Manager (MSM).

Adding support for Key Pair authentication in the Snowflake connector for MSM is critical for the following reasons:

1. It significantly improves the security posture of MSM integrations with Snowflake.
2. It ensures alignment with Snowflake’s supported authentication methods as password-based authentication is phased out.
3. It prevents potential production outages or blocked integrations if username/password authentication is fully removed by Snowflake.

Without this capability, customers using MSM may face service disruption of their Snowflake integrations once password authentication is no longer supported.