Leon Le

Problem Statement:

Customers are experiencing frustration due to the inability to selectively hide the "Open in Excel Online" button for specific tables in their environment - model-driven apps that were manually created. While the Ribbon Workbench tool offers a workaround, it is a community-supported solution and not officially maintained or endorsed by Microsoft.

Customer Need:

There is a clear demand from multiple users for a native, Microsoft-supported feature that allows administrators to control the visibility of the "Open in Excel Online" button at the table level. This would enhance governance, improve user experience, and reduce reliance on unsupported tools.

Current Limitation:

Although Ribbon Workbench provides a way to customize the ribbon, it is not an official Microsoft product. Customers are hesitant to rely on it for production environments due to concerns about long-term support and compatibility.

Request:

Introduce an officially supported configuration option within the Power Platform or Dynamics 365 admin settings that enables administrators to hide the "Open in Excel Online" button for selected tables in the model-driven apps that were manually created.

Currently, custom columns added to the Project - Grid view are fully editable.

Customers have expressed the need for greater control over these fields. Specifically, they would like the ability to configure certain custom columns as read-only, to prevent unintended edits and maintain data integrity.

Proposed Enhancement:

Introduce a setting or property that allows administrators to mark specific custom fields in the Grid view as read-only. This would improve governance and support use cases where data should be visible but not editable by end users.

Currently, custom columns added to the Project - Grid view are fully editable.

Customers have expressed the need for greater control over these fields. Specifically, they would like the ability to configure certain custom columns as read-only, to prevent unintended edits and maintain data integrity.

Proposed Enhancement:

Introduce a setting or property that allows administrators to mark specific custom fields in the Grid view as read-only. This would improve governance and support use cases where data should be visible but not editable by end users.

• Current Limitation:

In Dynamics 365 Customer Insights – Journeys, the CC feature for emails within customer journeys is restricted to recipients derived only from Contact or Lead entities. This limits flexibility in scenarios where journeys are initiated by custom or business triggers.

• Proposed Enhancement:

We propose extending the CC functionality to support custom and business triggers, allowing CC recipients to be dynamically added based on attributes or relationships defined in those triggers. This would mirror the flexibility already available for configuring the Email's From address, which can be set and get from custom triggers.

Customers need the ability to access and customize emission factors and other calculation values within the Calculate model using the Power Fx Experience. This is critical for adapting to region-specific rules and definitions.

Current Limitation

At present, only Activity values and custom values are accessible in Power Fx. Customers cannot retrieve or modify emission factors or other key values, which restricts their ability to implement localized calculation logic.

Business Impact

• Limits flexibility for customers operating across multiple regions.
• Prevents alignment with local compliance and reporting standards.
• Forces reliance on external workarounds, increasing complexity and risk of error.

Requested Enhancement

Expose emission factors and other relevant values in the Power Fx Experience to:

• Support direct referencing and customization.
• Enable region-specific logic and definitions.
• Improve transparency and control over calculation workflows.

We would like to request additional customization options for Autonumber columns in Power Apps to better support regional and operational needs.

Expected Behavior:

• Datetime Format:
• The Autonumber field should support custom datetime formats, including Singapore local time (SGT), instead of being limited to UTC.
• Segment Number (SegNum) Refresh:
• The SegNum component should have an option to automatically refresh daily, allowing for more dynamic and context-aware numbering.

Current Behavior:

• Only UTC datetime is available for Autonumber fields.
• SegNum does not refresh at all, limiting its usefulness for daily operations.

Impact:

This enhancement would improve localization support and enable more flexible numbering schemes for teams operating in different time zones or requiring daily resets.

In Customer Service Hub, specifically in the Account → Order view, there is a default active filter that appears even though customers did not create or configure it.

Currently, Power Apps does not provide any option to edit, hide, or remove this default filter. This limitation impacts flexibility and user experience when customizing views.

Please introduce a feature that allows administrators and makers to manage the default active filter in model-driven apps. This should include the ability to:

• Edit the filter criteria
• Hide or disable the filter if not needed
• Remove the filter entirely

This feature will:

• Improves customization and control over views in Customer Service Hub
• Enhances user experience by removing unnecessary or confusing filters
• Aligns with the principle of giving makers full control over app behavior