Usage guide: Dynamics 365 experience

The Dynamics 365 experience library pack enables EUC teams to:

Monitor usage to identify abnormal behavior and optimize the adoption of the application.
Proactively detect stability issues to troubleshoot and fix them before tickets can be created and/or employees can be impacted.
Measure and report on employees' experience with Dynamics 365.

Library pack uses

Jump to Use cases on this page to see relevant scenario applications.

Use the library pack content for the following purposes.

Monitor the adoption, speed, reliability, process efficiency and sentiment of your Dynamics 365 application and troubleshoot any issues directly from Nexthink Applications.
Use key pages and transaction data to analyze the most common Purchase-to-pay (P2P) and Order-to-cash (O2C) processes, such as customer master data management, sales order processing and purchase order processing.
Discover missteps or inefficiencies in the process, enabling your organization to identify and address bottlenecks, streamline workflows, and enhance productivity.

Visibility

This library pack's Microsoft Dynamics 365 Finance and Operations web application content provides comprehensive visibility into the application's adoption, performance, and stability. The preconfigured scope of key pages and transactions focuses on the application's Procurement and Sourcing and Sales and Marketing modules.

Use cases

In addition to the relevant use cases covered below, you may uncover other troubleshooting scenarios specific to your environment.

Measuring the performance of business process critical application pages

In Dynamics 365, each business process has its critical and less critical components. For instance, in Procurement and sourcing, the key element is the Purchase Order. To ensure these critical parts of the application perform well, use the predefined key pages to assess the situation.

Key pages that are frequently used and thus require optimal loading times include:

Inventory transactions
Released products
All purchase orders
All sales orders

The Speed—Page loads tab on the application dashboard allows you to easily assess the performance of individual pages.

Identifying inefficiencies in business processes

Business process inefficiencies can be identified using transaction data. Here are some examples of areas where improvements can be made:

Manual creation of purchase orders: Ideally, these should be generated automatically due to master planning. When purchase orders are created manually, they consume valuable time and increase the risk of human error. Automating this process ensures consistency and accuracy, allowing employees to focus on more strategic tasks.
Manual invoice posting: This process should be automated to save time and reduce errors. Manual invoice posting can lead to delays and discrepancies, affecting cash flow and vendor relationships. Automation streamlines the process, ensuring that invoices are posted promptly and accurately.
Frequent modifications to purchase orders: Each modification requires additional processing time and often necessitates further approvals, which can delay the process. Frequent changes to purchase orders indicate potential issues in the initial planning or communication stages. Organizations can identify and address the root causes by analyzing the reasons for these modifications, leading to more efficient and streamlined processes.

The Speed - Transactions dashboard captures these inefficiencies and helps target the right employees in the appropriate parts of the organization. By providing detailed insights into where and why these inefficiencies occur, the dashboard enables managers to implement targeted improvements. This enhances overall process efficiency and boosts employee productivity and satisfaction.