Dynamics 365 Field Service : Create and configure views

Views in Dynamics 365 Field Service are more than just lists—they are a powerful way to filter, sort, and present data that matters most to field technicians, dispatchers, and managers.

In this blog, we’ll explore:

  • What views are and why they matter
  • Types of views in Field Service
  • Step-by-step guide to creating and configuring views
  • Best practices for performance and usability

What Are Views in Dynamics 365 Field Service?

A view in Dynamics 365 represents a predefined filter and layout for a set of records. It determines:

  • Which records are displayed
  • Which columns (fields) are shown
  • How data is sorted and grouped

For example:

  •  “Active Work Orders” view shows only open work orders assigned to the logged-in user.
  •  “Products with Low Inventory” view helps inventory managers spot shortages at a glance.

Types of Views in Field Service


Step-by-Step: Create and Configure Views

1. Navigate to the Table

  •  Go to Advanced Settings → Customizations → Customize the System.
  •  Select the table (entity) like Work Order, Account, or Resource.

2. Create a New View

  •  Under the selected table, click Views → New View.
  •  Provide a name (e.g., “Open Work Orders - Technician”).
  •  Set a description for clarity.

3. Define Filter Criteria (FetchXML Query)

This is where you specify which records appear in the view:

  •  Use Add Filter to define conditions (e.g., Status = Open, Owner = Current User).
  •  Combine conditions with AND/OR logic for complex filters.

4. Configure Columns (Layout)

  •  Add columns you want users to see (e.g., Work Order Number, Priority, Due Date).
  •  Arrange column order.
  •  Set sorting rules (e.g., Priority descending).

5. Customize View Presentation (Optional)

For model-driven apps:

  • Apply column width adjustments.
  • Set default view for the table.

6. Save & Publish

  • Click Save and Close.
  • Publish Customizations to make the view available to users.

Best Practices for Views

  •  Limit Columns: Avoid loading too many fields—improves performance.
  •  Use Filters Wisely: The more complex the query, the slower the view.
  •  Default Views: Set logical defaults for common user roles.
  •  Leverage Personal Views: Empower users to create their own filters.
  •  Security Considerations: Only show sensitive data to authorized roles.

Final Thoughts

Mastering views in Dynamics 365 Field Service helps teams stay focused, act faster, and make informed decisions. Whether it’s dispatchers managing schedules or technicians prioritizing tasks, tailored views ensure everyone sees exactly what they need. 

Comments

Post a Comment

Popular posts from this blog

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

Connecting the Dots: FetchXML and Web API Integration in Dataverse

Image
 In Dataverse, FetchXML and the Web API are two powerful mechanisms for retrieving data and interacting with entities. Here's a brief overview of each and how they can be integrated: 1.    FetchXML :      -   Definition:   FetchXML is a proprietary query language used in Microsoft Dynamics 365 and Dataverse for querying data from entities.    -   Usage:   FetchXML queries can be used to retrieve data based on complex criteria, perform aggregations, and filter records.    -   Features:   FetchXML supports various query expressions, including conditions, sorting, grouping, and aggregation functions.    -   Integration:   FetchXML queries can be executed programmatically using client-side scripting, server-side code, or through tools like the Dynamics 365 Web API. 2.    Web API :      -   Definition:  ...
Read more