Dataverse Long Term Retention

The Long-Term Data Retention (LTDR) feature in Dynamics 365 offers significant benefits by enabling the archival of records into low-cost storage.

However, there are certain limitations that we hope will be addressed or included in the future roadmap:

1. Viewing Retained Attachments: Currently, the feature only displays the metadata of retained files without allowing access to the actual attachments. Providing functionality to view or download retained files would significantly increase adoption, as this limitation has made clients hesitant to leverage the feature.
2. Deleting Retained Records: At present, deleting retained records from Dataverse requires custom jobs utilizing SDK messages. Introducing an option to delete data from retained tables, similar to retention policies, would simplify operations and encourage broader use of this feature.

The customer is facing an issue with deactivating all Dataverse tables that are activated by default in the Azure Synapse Link setup.

During Fabric link export utility by default all data verse table get activate. But as discussed with PG team at this stage we can overcall the 1000 tables limitation but not disable the Dataverse tables.

So need option to de select the Dataverse table with fabric profile

Dear Microsoft Team,

I am a dedicated user of the Microsoft Arc Mouse and appreciate its sleek, portable design. However, I would love to see an enhancement that could significantly improve its functionality: integrating a touchpad mode for enhanced gesture control.

Currently, the Arc Mouse offers a smooth scrolling experience, but adding full touchpad-like functionality—such as multi-finger gestures for back/forward navigation, app switching, or even a pinch-to-zoom option—would greatly enhance its usability, particularly for those who rely on gestures for productivity.

This feature could be enabled through a firmware update or an additional setting in the Microsoft Mouse and Keyboard Center, allowing users to toggle between standard mouse mode and touchpad mode. Many users, including myself, would appreciate this flexibility, as it would bridge the gap between a traditional mouse and the intuitive gesture control of a trackpad.

I believe this enhancement would make the Arc Mouse even more appealing to professionals, students, and frequent travelers. I would love to hear if this is something your team is considering.

Thank you for your time and consideration.

Best regards,

Neli Vasileva

Intercompany and Direct Delivery orders are significantly contributing to the growth of customer's database, leading to usage overruns beyond the threshold.

Currently, there is no functionality to archive or clean up these types of orders, which limits customer's ability to manage database size effectively.

To address this, a propose developing a feature that allows for the archiving or clean-up of Intercompany and Direct Delivery orders. This feature should include criteria for archiving orders, such as orders older than a certain date or orders that have been fully processed and closed alongside the Inventory archival and not being allowed for data archival with intercompany chain linked to sales orders.

Additionally, an automated process should be implemented to periodically archive orders based on the defined criteria, along with a manual archiving option for users. It is also essential to ensure that archived orders can be easily retrieved if necessary for auditing or reference purposes.

Furthermore, a clean-up function may be developed to remove unnecessary data from the database, reducing its size and improving performance.

Implementing this archiving and clean-up function will help manage database growth, improve system performance, and ensure compliance with data retention policies.

However, it is important to note that addressing this issue will require additional resources and an increase in system resource requirements.

The impact of this issue is particularly significant for retail operations, where efficient database management is crucial for smooth functioning.

Hi Microsoft,

The description of an email with a modified date is currently moved automatically to file storage after 365 days.

It would be great if Microsoft could enable a feature to be able to allow the end user to amend (lower) Microsoft hard coded 365 day period. We have lots of clients that need to store emails as part of business continuity and legislation and with the email description being held in Database storage for a long period of time they have a constant challenge of trying to reduce data to ensure it stays within the restrictive capacity provided by Microsoft.

We understand that moving the email description to File storage removes the ability to search on the body of the email, but in the majority of cases this is not an issue. Our clients generally find emails based on the From or Subject field.

As you know we always have the ability to purchase more storage, but as of today 1gb per month at around £33 is something most SMB don't want to entertain.

Please can we request this functionality is added to the core Power Platform product.

Hi Team,

We are experiencing an issue related to the quick find search limitation

Although the return result limit is set to 10,000 records, we still expects a solution to extend this limitation. we want all results generated from the quick find search to be returned without this built-in design constraint.

when we create a Manual backup in sandbox instance it only retained for 7 days. there should be an option to extend the retention period as per requirement.

The multiple lookup control feature was introduced exclusively in the Field Service App. It is quite perplexing and somewhat challenging to understand why these functionalities have not been extended to all Dynamics 365 Customer Engagement (D365 CE) Apps.

By having this functionality natively available in the Customer Service App, we can ensure a more seamless integration and reduce potential complications associated with external dependencies. This would not only save time and resources but also enhance the overall user experience by providing a consistent and reliable solution within the Dynamics 365 ecosystem.

Implementing multiple lookup fields across all D365 CE Apps would significantly simplify the process of relating multiple records, as demonstrated by its current use in the Field Service App. Here are some points which can improve processes and user experience by providing the multiselect functionality across all the apps:

Enhanced Efficiency:

Users can quickly associate activities with multiple records without duplicating efforts, saving time and reducing manual work.

Streamlined Processes:

This feature can streamline workflows by enabling users to link relevant records directly, enhancing overall productivity.

Consistency Across Apps:

Extending these functionalities across all D365 CE Apps would provide a consistent user experience, making it easier for users to navigate and utilize the platform effectively.

I hope Microsoft will consider these points and roll out the multiselect lookup functionality across all Customer Engagement apps.

I have encountered a situation where two solutions are entangled in a circular dependency. To resolve this, we need all the dependent components of a solution within the circle to exist in order to untangle them. However, I have deleted all the dependent components in both solutions in lower environment, making it impossible to untangle the two solutions. I believe many people face the same problem. Therefore, I suggest implementing a function to address this circular dependency issue. Thank you!

Customers have an issue that after disabling appointment body synchronization between Dynamics and Exchange, appointments are still being tracked with their body/description. This is because the sync attribute configurations only affect Server-Side Sync, whereas the customer is tracking appointments with App for Outlook, which currently doesn't honor these settings.