-
A function to display a list of images of image data
Sometimes, users would like to change the icon for each entity in a model-driven app. However, when selecting the icon data users want to change, the icon image is not displayed, so it is difficult to change. It would be convenient to have a function to display a list of images of image data saved in Web resource. -
Product import cannot be completed successfully when duplicate unit records exist on unit groups
Some users would like to create unit groups by product types. Units created on unit groups sometimes duplicate between records. In this case, product records import cannot be completed successfully due to duplicate records. It would be much better if product data successfully are successfully imported even though duplicate unit records exist on unit groups -
Upload files by drag and drop to Dynamics
Dynamics and SPO integration settings allow us to upload files from Dynamics to SPO.
https://docs.microsoft.com/en-us/power-platform/admin/set-up-dynamics-365-online-to-use-sharepoint-online
When uploading a file to Dynamics, the current design requires us to click the upload file button.
If this could be uploaded by dragging and dropping the file, it would be very convenient.
-
Please plan to increase the number of components that can be added to the dashboard.
As noted in the Docs below, the maximum number of components we can currently add to a dashboard is six.
https://docs.microsoft.com/en-us/dotnet/api/microsoft.xrm.sdk.deployment.dashboardsettings.maximumcontrolslimit?view=dataverse-sdk-latest&viewFallbackFrom=dynamics-deployment-ce-9
It is very small that we can add up to 6 components.
We can't fully use the convenience of the dashboard.
We would like to increase this limit to 6 or more.
Will it make our business more accelerated!
-
Audit logging enhancements
Currently, Dataverse audit logging primarily logs about CRUD of records.
Also, the user's system access log is not recorded again for 3-4 hours once it is recorded.
It would be even more useful for us if Dataverse's audit log could also output the following events:
・Audit logs for table and app metadata changes
・ Audit log that records the log of the user's access to the system each time authentication occurs
・Access and CRUD logs related to Power Apps Portal
-
Decouple Inspection Template Number Questions from "Pricing Decimal Precision" Setting
💡 Description:
Currently, the decimal precision of Number-type questions in Inspection Templates is affected by the "Pricing decimal precision" setting in environment behavior settings (PPAC > Environment > Settings > Behaviour).
This behavior is confusing and unintuitive for the following reasons:
- Number questions are typically used for general numeric inputs (e.g., temperature, quantities, scores), which are not related to pricing or currency.
- The "Pricing decimal precision" setting is intended for controlling decimal places in currency fields, as clearly documented.
- Customers are reluctant to change this setting, as it also affects existing Dataverse currency fields across the environment.
- This hidden dependency can lead to inconsistent behavior, especially when using different base languages (e.g., English environments default to 2, Japanese environments default to 0).
🎯 Proposed Improvement:
Please consider decoupling the precision of Number-type questions in Inspection Templates from the "Pricing decimal precision" setting.
Instead, allow these questions to:
- Have their own explicit precision setting, or
- Default to a reasonable number of decimal places (e.g., 2), independent of pricing-related configurations.
🔍 Business Impact:
This behavior is currently blocking customers from using decimal values in Number-type questions without affecting global currency formatting.
It creates avoidable confusion and increases the risk of unintended side effects when adjusting a setting that is supposed to affect only currency fields.
You’re offline. This is a read only version of the page.
