It would be great, if the import performance will be optimized. It seems, that adding new languages to the system slows down the import extremly.

For example:

• Starting the import of a solution takes for example 10 minutes to complete.
• After installing 10 additional languages into the system, the same solution takes 20-times longer (=200 minutes) to import.

It is possible to filter out some data via the quick find view of an entity. This excluded data should also be not findable via the dataverse search. As all the config for the dataverse search goes via the quick find view, the exclusion of data should also be part of this.

I have an idea by means of which we can Ehance Performance of Windows what we can do is we can creat partation in main memory using os in Alphanumeric way suppose we want to seach something form memory staring with letter a so we need to just look a that block which is assinged to a so it will increse the overall performance , I don't know if windows have this feature or not but I was curious to share this with microsoft

Thank you

I have a retention policy created but not matter when I schedule it for the Status of it is always "Deactivated". How do I make it actually run.

Background & Challenge:

In the current data management landscape, many organizations leverage Azure Data Lake for data storage and analytics. However, they often encounter a significant challenge in the process of integrating data, particularly when using managed tables that are not customizable. A key issue is the absence of a "track changes" feature in these tables. This feature is crucial for synchronizing data via Microsoft tools like Power Apps - Synapse Linked are involved in the data pipeline. Without the ability to track changes by default, users must implement workarounds, leading to increased complexity, risk of data inconsistency, and potential delays in data availability. This limitation hinders the agility and effectiveness of data-driven decision-making processes.

Idea Description: AutoTrack

The proposed solution, "AutoTrack," is designed to address this gap by setting the "track changes" feature as a default option in dataverse managed and non-customizable tables. AutoTrack aims to streamline the data integration process, enhancing the efficiency and reliability of data synchronization between dataverse and Azure data lake.

Key Features:

• Default Change Tracking: Automatically enables tracking changes in managed tables, eliminating the need for manual setup and ensuring that any alteration in the data is captured seamlessly.
• Enhanced Integration with Power Apps - Synapse linked with Azure Data Lake: Optimizes the data flow from Power Apps to Azure Data Lake via Synapse link, ensuring real-time data availability and consistency.
• Data Lake Optimization: Improves the overall efficiency of Azure Data Lake by ensuring that only relevant, change-impacted data is processed and stored.
• Simplified Data Management: Reduces the complexity of data operations, making it easier for users to manage their data landscapes without deep technical expertise.
• Improved Data Quality and Consistency of table schemas: Ensures that data across the organization is up-to-date and consistent, facilitating accurate analytics and decision-making.

Impact:

AutoTrack will significantly reduce the technical barriers and complexities involved in data integration into Azure Data Lake. It offers customers more freedom and flexibility in managing their data, leading to enhanced data quality, better analytics, and more informed decision-making. This feature is particularly beneficial for organizations looking to leverage the full potential of their data in a cloud environment without the additional overhead of manual change tracking configurations.

We have added the few tables to azure synapse link, using one lake configuration, but we are unable to remove the already added tables from the synapse link.

Scenario: Added few tables out of that we need to remove few tables, but not able to deselect the tables.

MS Responded that, it is a standard functionality. it will be better if we can remove and readd the tables.

Thank You.

Test

getsg

We would like to suggest the field setting business required in Dataverse should be a physical restriction.

If the field setting business required is only a soft restriction, then we have to do a lot of extra development for complete the physical restriction.

We look forward your comment soon, thank you.

In some cases where you have data and associated docs (ie., pdf, word,etc) that need to be managed from a retention policy perspective. It would be nice to be able to have a policy that's configured to handle both. Thoughts?

Issue -

When reporting from the phone call exported data the to and from fields contain the same guid as the phone call itself instead of the guids of the chosen lookup records.

Ask -

Yes we ultimately did use activity pointers as a workaround but it is extremely slow and taxing sql operation. Is there any reason the To and From fields on the phone call entity are designed this way? In future we should think about storing phone call recipient information in phone call entity table along/instead of activityparty base table.