{"id":77368,"date":"2017-10-23T09:38:44","date_gmt":"2017-10-23T14:38:44","guid":{"rendered":"http:\/\/www.beringer.net\/?p=77368"},"modified":"2017-10-23T09:38:44","modified_gmt":"2017-10-23T14:38:44","slug":"system-views-vs-my-views-part-one-of-two","status":"publish","type":"post","link":"https:\/\/www.beringer.net\/beringerblog\/system-views-vs-my-views-part-one-of-two\/","title":{"rendered":"System Views vs My Views – Part One of Two"},"content":{"rendered":"

Which are better? Which should I use for my organization?<\/h3>\n

There is no definitive answer to either of these questions as the answer is based on each unique organization. To answer this question for you, I would have to ask you some questions as well. How many system views do you currently have setup for your entities? How many of these views do all<\/span> of your users use? We’ll talk about your answers shortly.<\/p>\n

What is the difference?<\/h3>\n

Let’s start with some definitions.<\/p>\n

System Views<\/strong> are views that are available to any user who can access the entity. They are managed by system administrators or system customizers. The only way to block specific users from seeing system views is by removing their access to the entire entity.<\/p>\n

\n
\n
Just because a user can see and select a System View from the list does not mean that they can see all of the records in that view. They can only see records within views that they have access to see. This is true of both System Views and My Views. For example, if you have business unit security setup and it is based on Territories or Regions, a user who can only see accounts within certain states will only see those records when they select a view showing All Active Accounts. Whereas a system administrator in the Parent business unit, who has the highest level of security, can see all records across all Territories\/Regions when accessing the same view.<\/div>\n
<\/div>\n
\u00a0\"\"<\/div>\n<\/div>\n<\/div>\n

My Views<\/strong> are views that a user has saved through an Advanced Find. They are personal views that only the owner of the view can see, unless they share it with other users and\/or teams. The system administrator can manage the users’ access level to My Views by updating the Saved View entity in security roles.<\/p>\n

You can easily copy a System View to view under My Views but you cannot copy a view under My Views to a System View. You will not see the heading My Views in the view list until you save an Advanced Find.<\/p>\n

Which is best for you?<\/h3>\n

There is no one-size-fits-all answer. If your organization has a long list of System Views and your users are not using all of the views but rather are using a subset depending on their role, then as a System Administrator, you might want to consider using My Views and sharing them with teams. How to do this will be covered in Part Two.<\/p>\n

You may want to evaluate your System Views as well. Are you setting up new views with the same columns but with different filter criteria for each Territory\/State or for each Service your company offers? In this case, you can setup one view and simply provide training to your users on how to use filtering or use the new grouping feature in D365.<\/p>\n

Even if you decide to use My Views and share with Teams, you’ll still want to assess your current list of views to determine where you can consolidate prior to making any changes.<\/p>\n

What\u00a0can I\u00a0Do Now? Where Do I Start?<\/h3>\n

A best practice for any Views is to use Filter Criteria to its fullest capabilities. Anytime you can use dynamic values instead of hard-coding a value, do it! Here are a few examples:<\/p>\n