Dataverse Long Term Retention

Our environment has encountered a 1,000-attribute limit on the entity/table in D365, necessitating a rearchitecture of our usage. We propose increasing the attribute limit to 2,500 to accommodate larger data collections and prevent similar issues. This change would support smoother implementations and ongoing operations, such as enabling the installation of CJI and other applications.

I am using Dataverse and building a Model-driven application in Power apps. Right, there is not functionality that allows to format a decimal column as % or $ I know that it is posible to define columns as currency but there is a los of limitations using in Power automate and defining formula columns, Rollups. Also, will be nice to include the same functionality for formula columns when th result is a decimal by example for calculation of the amount using the quantity and Unit price

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.

We would like to suggest an idea that the URL field format can be modified such as automatically adding the key "https://" before user type in a link.

Also, we suggest that the error message when we type incorrect format can be changed to fit with different scenarios.

Hello,

I got this link from your support and I can't find the right category though please send this bug to the right team:

Every time after the update of Power Automate Desktop the variable Microsoft.Flow.RPA.UIFlowService.ScreenDefaultResolutionEnabled in the UIFlowService.exe.config is set to false. Though I have to change every time back to true after update.

Please fix this bug.

Thank you very much.

Best regards,

Julia Pfeiffer

本公司长期专业代做中国银行存款证明●+微{Q}181286291●银行流水账单以及代办银行存款证明.代开工作收入证明(可回访),代办个人完税证明,修改个人征信报告,办理的银行有:农业银行、建设银行、工商银行、招商银行、中国银行、交通银行、邮政储蓄银行、农商银行、兴业银行、民生银行、浦发银行、上海银行等.

核心技术团队

本公司核心技术骨干均是在银行流水服务行业拥有多年经验的精英。丰富的实战经验，娴熟的专业技能，可为个人或企业稳定快速高效的运行提供全面的技术支持。除了各自掌握的专业技能不同之外,我们拥有共同的理想、共同的目标、共同的信念。我们始终如一,无论是对待客户,还是内部成员，都是以思考+沟通为核心，将各种专业技术、创意与策划为一体,以十二万分的热诚,将具有不断更新突破,集战略、高效、创意于一体的解决方秦交付给每一位客户，

银行存款证明 

    存款证明业务是指银行为存款人出具证明，证明存款人在前某个时点的存款余额或某个时期的存款发生额,和证明存款人在银行有在以后某个时点前不可动用的存款余额。个人存款证明是客户因出国留学、探亲、旅游、移民定居、经商或其他目的需要开具的资信证明。

售后服务团队

我们的客服推行24小时“快速响应、立即行动“的服务机制。我们拥有靠谱的客户关系管理系统，为客户提供“标准化流程化服务”:不但有健全的客户关系维护体制;健全的客户培训体系:还有“一条龙式”的客户满意度跟踪体系，只要是我们的客户,不论大小，我们永远提供优质的服务。

Per document below, it's stated that SharePoint doesn't fully support ALM scenarios.

There are issues in correctly updating the references to SharePoint in the environment where the solution is imported. It means that SharePoint meta-data (for example, a new column has been added) or data source info (for example, a list pointed at) will be wrong. Refreshing Power Apps Studio in the target environment won't get additional metadata and the data source will always point to the data source for the source environment

Data source references based on environment variables aren't updated during solution import - Microsoft Dataverse | Microsoft Learn

Since it's not fully supported, this option should be removed and updated on the document to avoid confusion for the customer.

Allow updates to 'Regarding' lookup columns using a dataflow.

Include details on how additional capacity was purchased (e.g. data purchased from vendor, allocated via licenses, etc) in the Power Platform admin center under Resources, Capacity, and Storage Capacity by Source, and Additional Capacity.

With elastic tables having recently gone GA some of the limitations of cosmosdb query which you can get round using User Defined Functions in a full cosmosdb installation you cannot do in Dataverse due to having no UI, way to implement.