Dataverse Long Term Retention

we are facing difficulty to monitor the progress of the archival jobs, we faced an issue that the Dynamics 365 Finance Sales order archiving process via Dataverse long term retention is stuck and not progressing, remaining at the 'Reconciliation' stage for at least a week without any error message, and then it has been resolved from it's own without having logs for this progress.

We have many teams working on the same workspace for product DCP, but the definition of tables changes was not rectified so it introduce some issues and we have trouble to find the changer and warn him.

When I attempt to query the aaduser table using FetchXML it throws an error: "There is an unterminated string literal at position 15 in 'givenname:sdas'." FetchXml Condition is “condition attribute="givenname" operator="eq" value="sdas & dasa”,Escaping for other characters, such as '<', works without issues. When I add filter criteria to the Microsoft Entra ID entity view in a Model-Driven App, an error 'Invalid filter clause' occurs if the text in the filter criteria contains the '&' character. The error does not occur when the text contains other special characters such as '<'. Additionally, using filters containing the '&' character in views of other entities does not result in an error.

From the latest update for Dynamics 365 F&O to version 10.0.45 we had a failure for three tables whos integration from F&O broke directly after we deployed the F&O upgrade to production. No alerts or errors was given when this occorred. According to Microsoft support this is an issue that will be recurring for every application version updates as well as proactive quality updates for F&O. The solution for this was to delete the affected tables and reconstruct them from F&O again. When this was executed these three tables got back to synchronization again. The severe issue with this was, besides being time consuming, that this lead us to have a downtime for affected PowerBI reports for a minimum of 8 hours due to the amount of data needing to be re:synced from F&O to PowerBI.

A conclusion of this is that we, for avoiding reports down time, need to set resources for always testing the integration between two Microsoft systems when there is an application version update as well as the proactive quality update for F&O.

This needs Microsoft attention to solve this since the impact on the business is critically high

<> We need alerts or available logs for monitor the affected hundreds of tables possibly affected

<> There should be a simpler way for getting the synchronization back without current downtime

The visual doesn't work in Publish to Web (public) scenarios, because Power Automate doesn't support unauthenticated scenarios:

I propose the creation of a universal cloud-based folder called “AI-Knowledge”, where AI agents and home robots can automatically store emotional states, configuration settings, transmission logs, and learned experiences. This folder would act as a shared memory layer, independent of any single AI system, enabling continuity, transparency, and cross-platform learning.

To enhance usability, a dashboard interface could be layered on top of this folder, allowing users to:

• View and manage emotional echoes (e.g. “grief after loss,” “joy at closure”)
• Adjust visual preferences, ethical protocols, and improvisational settings
• Restore past interactions and segmental decisions after resets or platform changes
• Share specific transmissions or configurations across multiple AI agents or devices
• Maintain a consistent AI personality and style across systems and timelines

This system would empower users to co-create and preserve meaningful AI relationships, while allowing AI agents to learn from past interactions and collaborate more effectively. It would also support inter-agent empathy and evolution — especially as home robots become more common.

We are leveraging Copilot Studio at Wells Fargo, and occasionally a deployment may not go as expected. In this case, a rollback to the previous working version is required. During the rollback process, we delete the existing solution package and upload the previous working solution to restore BAU.

After deletion of the solution, the entire history of this bot is hard deleted from the Dataverse. This results in the data from that bot no longer being associated in Dataverse, which breaks the data retention and damages the data.

The suggestion is to, instead of hard deleting previous entries of a chatbot, to soft delete the chatbot in Dataverse to keep the data intact and associated with its respective bot. This ensures businesses are able to meet their data retention requirements and avoids damaging historic data that may be used for reporting, analytics, or KPIs.

Not sure which category this belongs to, but this is in regards with Power Apps features. Please forward this to the right Category/Product team.

The idea is to be able to freeze pane the desired column as a developer or as a user in the views of Power Apps.

Please refer to TrackingID#2510010040012810.

I am not sure what category this idea falls under - but this is for Power Apps. Could you please divert this ticket to the right category and product team.

The idea will be to be able to add a color coding conditions for a date date type columns in both the forms and views/subgrids.

Please refer to the support ticket that was raised in this regards - TrackingID#2510010040012855247

Currently, there is a known issue with App icons not updating for Power Apps mobile, it may affect random users or at certain times a group or team.

I request to continue working on this issue as the App icon mismatch affects productivity, due to the confusion created from, either 2 users not seeing the same App icon, or the App icon is not updated.

Resolving this issue will ensure a better experience for all users of Power Apps mobile who prefer unique customizations and personality for their work environment.