User Review
( votes)Saved views has been one of the interesting features of Microsoft Dynamics 365 Finance and Operations and was released as a preview in PU32 (if my memory serves me). With PU36, it is under GA and is one of the promising UI and low- to no-code productivity improvement features that should not be missed. That said, if you need some background about saved views, then review the documentation.
Let me share more about the experience of working with Saved views and how to get started.
One of the common requirements/pain points of Dynamics 365 Finance and Operations (D365FO) arises when there is an interface like a form or dataset that is shared by multiple teams and they want to have both a set of standardized views for the team. Sure, D365FO has robust personalization and that can even be shared, but that is for individual users. How about the ability to create a consistent view for all team members and share it with all of them? How about having one view for a particular set of users/roles and one view for another set of user/roles? Sounds interesting? That’s what Saved views intends to solve.
Let us take the classic example of All Vendors. This dataset/form is usually shared by two teams in any organization: Procurement and Accounts Payable. Each of these teams have different view requirements for vendors. Each of these teams requires adequate access, however they would want to limit the visibility of other out of the box options without restricting them fully.
Below is a Standard view of the All Vendors form that is available OOTB.
In the image below I have personalized a view that has the majority of the columns that usually an AP Processor would like to view.
