Know Your Users: Automated Usage Tracking for Better System Adoption

-

Introduction

After a new Business Central system goes live, it’s important to know if users are actually using it the way they should (Go-Live is just the beginning).
Tracking usage statistics helps us understand how well the system is being adopted and where improvements might be needed.

To make this easier, I’ve created a small utility that automatically collects user activity data and builds a report from it.
This saves time and gives a clear picture of how the system is being used to the management.

Here’s what it does:

  • There’s a setup page where you can choose how stats are collected and skip certain users (like consultants or support team members who create test data).
  • A configuration page lets you pick which tables to track.
  • You can also set how often stats should be gathered using a frequency field; it even sets up the background job for you.
  • A report which summarises the generated data in a neat matrix.

With this tool, keeping an eye on system adoption becomes simple and automatic.

I've also added an API which exposes the statistics data and created a basic Power BI report with it.

Results






Conclusion

A customer should always get the full value from the system they've invested in and at the heart of any ERP is data.
If users are struggling to generate or work with that data, it's up to implementation partners to identify and fix those pain points.
Automating the collection of usage statistics is a simple yet powerful way to improve visibility into system adoption.
It gives clear, measurable insights that help drive better support, stronger user engagement, and ultimately, greater customer satisfaction and retention. 
After all, a happy customer isn’t just a win today; they’re a long-term reference for the future.

Comments

Post a Comment

Popular posts from this blog

Event-Driven Architecture: How to Create Custom Business Events in Business Central

-
Image
Introduction Events are notifications that signal something has happened in the system. A record getting created, updated or deleted, a sales order getting posted, etc are all examples of events. An event driven architecture provides asynchrony and decoupled communication between different components of the system supporting flexibility, scalability and modularity. In Business Central, we have two main types of events - Business and Integration. Integration Events are related to things within Business Central. They are use for extending the functionality of the Base Application without modifying it directly. Business Events are related to things outside of Business Central. They are used for notifying external systems (e.g., via Power Automate or Logic Apps) regarding any changes that happen within Business Central. Microsoft allows us to create custom Integration and Business Events based on our requirements. In this blog, we'll see how to create a custom Business Event and...
Read more

Leverage Postman for Streamlined API Testing in Finance and Operations

-
Image
Introduction Postman is a tool for testing APIs. It lets you send requests, automate tests, and share your work with your team.  We're going to connect Postman to our Finance and Operations environment so we can test out standard or custom APIs. I've already covered automating the testing in Postman in my blog here  so once the connections are in place you'll be good to go! Pre-requisites Postman Finance and Operations Environment Configuration We'll start with creating an App Registration in Azure Portal. Go to the Azure Portal (of the same tenant of your FnO Environment). Search for "App Registration" and click on "New Registration". Add a name for your new app and click on "Register." Once it is completed, you'll be taken to the Overview of the app. Here, click on the "Add a certificate or secret" under the "Client Credentials." Add an appropriate name and select the expiration date of the certificate as necessary...
Read more

Integration with Finance and Operations - From Basics (Part 2)

-
Image
Introduction Finance and Operations provides two major ways to interact with tables (or data entities) for external system using APIs; namely Custom Services and Data Entities. Data entities in D365 Finance and Operations simplify data management by grouping data from multiple tables. They make it easier to import, export, and integrate data with other systems. Custom services in D365 Finance and Operations allow developers to create web services for specific business needs. They enable external systems to interact with D365 F&O by exposing custom logic and operations. This helps in integrating and automating processes with other applications. In the previous blog, we saw how we can use Data Entities to create APIs. In this blog, we'll see how we can use Custom Services to create APIs. References Custom Service Development Exposing an X++ Class as a Data Contract Using Data Contracts Pre-requisites A Finance and Operations Environment Postman connected to FnO Enviroment (If you...
Read more