-
Addition of Storage Size Estimation Feature when "Change History" is Enabled
Currently, the feature for estimating storage size when "Change History" is enabled is not available.
The addition of this feature is expected to improve user convenience and further enhance operational efficiency.
-
Request for Adding a Feature to Use Add-ins for Dynamics 365 and Copilot for Sales from Outlook and Teams in a Multi-Tenant Environment
Currently, in a multi-tenant environment, it is not possible to use the add-in functionalities of Dynamics 365 and Copilot for Sales from Outlook or Teams to reference data.
The addition of this feature would enhance user convenience and further improve operational efficiency.
-
Addition of the Feature to Export a List of Tables Occupying File Capacity in CSV, Excel, etc.
Currently, there is no feature available to export a list of tables occupying file capacity in file formats (CSV, Excel, etc.).
However, we believe that the addition of this feature would enhance user convenience and significantly improve operational efficiency.
-
Control Feature for Cases Where Required Fields Are Unfilled During Excel Import on the Model-Driven App View Screen
Currently, on the model-driven app, there is no control feature to prevent records with unfilled required fields from being imported as errors when importing Excel from the view screen. The addition of this feature is expected to improve user convenience and further enhance operational efficiency.
-
Request for the addition of functionality to retrieve the username of the user who made the actual modification and to check the date when "Project for the Web ModifiedBy" was updated, when using the "Project for the web ModifiedBy (msdyn_pfwmodifiedby)" field in the project table.
Currently, when attempting to track the name of the user who made the most recent changes in the Project app, even when utilizing the "Project for the web ModifiedBy (msdyn_pfwmodifiedby)" field in the project table, there is no functionality to retrieve the username of the user who made the actual modification, nor is there a feature to check the date when "Project for the web ModifiedBy" was updated.
We believe that the addition of these features would enhance user convenience and contribute to the improvement of operational efficiency.
-
It is not possible to change the maximum length of the primary column after creating a table in Dataverse.
Currently, Dataverse does not provide the capability to modify the maximum length of the primary column once the table has been created.
We believe that adding this functionality would improve user convenience and further enhance operational efficiency.
-
We would like to request the addition of a feature in Dataverse's duplicate detection rules that allows the match code length to be counted based on the maximum length defined at the time of primary column creation.
Currently, when specifying a primary column in Dataverse's duplicate detection rules, the match code length is counted as 850 characters, even if the maximum length of the column is set to 850 or less at the time of creation.
There is currently no functionality that counts the match code length based on the actual configured maximum length.
We believe that adding this feature would improve user convenience and further enhance operational efficiency.
-
Request for the Addition of a Feature to Add Conditions to the Real-Time Marketing Lead Scoring Model in Customer Insights-Journeys Without Stopping Live Activation
Currently, there is no feature available that allows users to add conditions to the lead scoring model without stopping the live activation. We believe that the addition of this feature would enhance user convenience and further improve operational efficiency.
-
Request for Improvement Regarding Error Occurrence When Related Entities Are Used Multiple Times in Views with Multiple Link-Entities in FetchXML
We have confirmed that the current behavior—an error occurring when loading task lists in the "Focus View" if related entities are used twice within a view and two "link-entity" elements are configured in FetchXML—is the default operation.
This issue occurs because the same related entity (link-entity) is used twice with identical relationships in both the "to" and "from" attributes.
However, in Personal Views or customized system views, there are many cases where setting multiple "link-entity" elements in FetchXML is necessary.
We believe that improving this behavior would enhance user convenience and contribute to further increases in operational efficiency.