Dataverse Long Term Retention

I dont know

Rationaliziw subbing hibbbsy ihhsn igss shuhejdhjdhjdehdjdhejfrfjuyrsgtjymrewtgfdsr,uteygurjeghdrujgysdk,fsgdfhregreyfuewgfujfgsudf

When Environments are copied from in admin portal the dataflows are not copied or at least do not show up in the dataflow area. They do however exist in the Dataverse table called dataflows. because of this trying to import a solutions containing managed dataflow will fail with an obscure error. The only way to fix this is to delete the records form the dataflow table and re import the managed solution. The issue is that you can't delete data flow records that are marked as managed... If you can't copy the dataflows and make them available in the target environment, then the records for those dataflows in the dataflow table should be removed allowing the next solution import to import the dataflows.

Example the production environment is copied to a new UAT environment we then import the latest solution changes for testing, but the import fails because the dataflows are missing.

It would be useful to tag D365 related read logs while exporting them (automatically) to O365 security and compliance center. Also possibility to retain those logs for longer than just 90 days would be beneficial.

Give Provision to delete Audit records with Event Type Audit Log Deletion and also give the provision to delete specific entity records with Timeframe as this will help to retain only specific records with specific timeframe.

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.

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

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.