Dynamics 365 Field Service : Manually update inventory by using inventory journals
Managing inventory effectively is critical for Field Service organizations to ensure the right parts are available at the right time. Dynamics 365 Field Service offers Inventory Journals to manually adjust inventory quantities for warehouses, vans (Field Agent stock), and other locations.
This article provides a deep-dive into inventory journals, their technical structure, and step-by-step guidance on how to use them for manual updates.
What Are Inventory Journals in Dynamics 365 Field Service?
An inventory journal is a record of manual inventory adjustments. It allows technicians, warehouse managers, and back-office staff to:
- Add or remove stock quantities.
- Correct discrepancies (e.g., physical count mismatch).
- Record transfer of stock between locations.
- Track all changes for audit and compliance.
In Dynamics 365, inventory journals are stored as Inventory Adjustment (msdyn\_inventoryadjustment) entities and use Inventory Adjustment Product (msdyn\_inventoryadjustmentproduct) as child records.
How Inventory Journals Work Technically
Here’s how Dynamics 365 handles an inventory journal under the hood:
When you post an inventory journal:
- The quantity adjustments update msdyn\_inventory (inventory levels).
- Changes are reflected in work orders, ensuring accurate stock availability.
- Audit trails are created in the system for tracking.
Common Scenarios for Manual Inventory Updates
Step-by-Step: Manually Update Inventory Using Journals
Step 1: Navigate to Inventory Adjustments
1. Go to Field Service > Inventory > Inventory Adjustments.
2. Click + New to create a new journal.
Step 2: Enter Header Information
- Name – Enter a meaningful name (e.g., “Van Stock Correction – July 2025”).
- Warehouse – Select the warehouse or location where stock is adjusted.
- Owner – Defaults to the current user.
- Adjustment Date – Defaults to today; you can backdate if needed.
Step 3: Add Products to Adjust
1. Under Related > Inventory Adjustment Products, click + Add New Inventory Adjustment Product.
2. Fill in the fields:
Step 4: Review and Post Journal
- Review all line items for accuracy.
- Click Post Adjustment.
This triggers:
- Update of inventory quantities in `msdyn_inventory`.
- Creation of audit records for traceability.
Key Considerations & Gotchas
✔ Stock Ownership
- Dynamics 365 tracks stock ownership (e.g., Customer Owned, Company Owned). Ensure you pick the correct type.
✔ Warehouses & Bins
- If you use bins within warehouses, the adjustment must specify the bin location.
✔ Async Inventory Updates
- Inventory recalculations post asynchronously. Allow some seconds/minutes before the changes reflect in Work Orders.
✔ Security Roles
- Users must have proper Field Service security roles (Inventory Manager or Dispatcher).
✔ Field Agent Scenarios
- If using mobile app, agents can initiate adjustments directly in the field (online or offline).
Advanced: Automating Inventory Journals with Power Automate
Did you know you can automate repetitive inventory adjustments?
Example: Create a Power Automate flow to:
- Trigger on physical count completion.
- Create `msdyn_inventoryadjustment` records.
- Post them automatically.
This is ideal for large organizations with regular stock reconciliations.
Why Use Inventory Journals Instead of Direct Edits?
Unlike direct edits to inventory, journals provide:
- Audit trail for compliance.
- Granular reasons for adjustments.
- Integration with Field Service workflows.
- Mobile and desktop support.
Final Thoughts
Manually updating inventory using journals in Dynamics 365 Field Service ensures accuracy and transparency in stock management. It’s an essential tool for organizations aiming for operational excellence and regulatory compliance.
By understanding both functional flow and technical design, you can empower your field agents, warehouse managers, and back-office staff to maintain clean and correct inventory records.
Published on:
Learn moreRelated posts
Power Platform Environment Deep Dive (Part 2)
In Microsoft Power Platform, choosing the right environment type is important because each environment is designed for a different business pu...
Power Platform Environment Deep Dive (Part 1)
Today, in the business enterpriese world, Power Platform enables organization to build application, automate workflow, analyze data crea...
Book Review : Life 3.0 by Max Tegmark
This is the third book I’ve read this year, and even though I’m still in the early chapters, it already feels like my favorite read of the yea...
Dataverse Views Demystified: Making Data Work for You
In Microsoft Dataverse, users do not always see all the data stored in a table. What they can view depends on their security permissions, role...
Decode & Fix : Shared App host initialization has timed out in Microsoft Power Apps
Issue :While working with apps in the Microsoft Power Platform, we encountered a critical issue where the application failed to load pro...
Dataverse Integration Patterns: Sync vs Async vs Event-driven (Real Use Cases)
As organizations start using Microsoft Power Platform, Microsoft Dataverse is no longer just a place to store data—it becomes a key part of ho...
Book Review : Don't Believe Everything You Think by Joseph Nguyen
My second book of this year is "Don’t Believe Everything You Think" by Joseph Nguyen. This book was recommended by a friend who strongly belie...
Book Review : Scary Smart by Mo Gawdat
The first book I read in 2026 was Scary Smart by Mo Gawdat, the former Chief Business Officer at Google.In today’s world, Artificial Intellige...
Managing Temporary User Access in Dataverse with Access Teams
Access Teams let you give people access to one specific record, not the whole table.Access Teams in Microsoft Dataverse are a powerful way to ...


