Comments
It is difficult for our users that at the start of each new quarter they lose visibility of emails that are still in progress. It is true that the visibility period can be adjusted, but every time this is done the filters have to be reapplied… a tedious, time-consuming, and confusing process. This improvement is essential for the adoption of the tool.
This enhancement is highly needed by many customers who have migrated from NAV to Business Central.Several of our customers have a large number of NAV/BC users, and one of the most common feedback points is the lack of the filter append functionality that was available in Navision. Users are becoming increasingly frustrated because they now need to manually enter and maintain filter values, which consumes significant time and reduces productivity.To address this gap, we have even had to provide customizations for multiple reports without raising formal change requests, simply because customers relied heavily on this functionality in their daily operations.A frequent comment we hear from customers is:"We were able to do this easily in Navision. Why is it not available in Business Central?"During migration discussions, customers are often told that NAV functionality will continue to be available while Business Central brings additional capabilities. Therefore, preserving commonly used and productivity-enhancing features such as filter append would greatly improve the user experience and ease the transition from NAV to BC.I strongly support adding this feature in an upcoming release and believe it would provide significant value to many existing NAV and Business Central customers.
In the documentation it is suggested to use the "Reset Microsoft Templates" action.And there is a caution section ... informingThe Reset Microsoft Templates action resets all of the Microsoft workflow templates. You can't reset a single template.Fair enough. But actually this function does not only reset the templates. It destroys existing workflows if the name of the workflow, created from a template, has not be renamned and still starts with 'MS-'There seems to be no hint / no recommendation to change the name of a workflow in order to prevent losing all workflow steps on reset.A simple warning or confirmation dialog is the bare minimum, but it's not really enough.This function should really only modify the workflow templates and add new templates — it must not destroy existing workflows!
Business Impact====================- This gap is a significant blocker for enterprise-wide Power Platform adoption, particularly for organizations implementing strict environment governance and developer environment strategies.- While M365 Copilot and other Power Platform experiences already honor environment routing policies, Workflow creation from Teams, Outlook, Office apps, OneDrive, and SharePoint bypasses these controls and always targets the Default environment.- The resulting governance inconsistency creates operational burden, increases compliance risk, and prevents customers from fully implementing their intended platform management model.- Several customers have indicated that alignment of Workflow creation behavior with existing environment routing capabilities is critical for long-term Power Platform adoption and governance at scale.