MS Learn Highlights – 7/10/2025
Modern workflows in POS
This article describes how modern workflows in the Microsoft Dynamics 365 Commerce Point of Sale (POS) enhance usability, extensibility, and accessibility for store commerce operations.
Key Improvements
- Usability: Streamlined POS interfaces enable faster and more intuitive interactions, reducing training time and increasing cashier efficiency.
- Extensibility: The POS architecture supports easier integration with third-party services and customized components, allowing retailers to tailor POS functionality to specific business needs.
- Accessibility: Improved accessibility features ensure compliance with standards, making POS usable for a diverse workforce, including those with disabilities.
Highlights of Modern Workflows
- Redesigned POS screens with simplified navigation and workflows tailored to common retail tasks.
- Modular and customizable UI elements let retailers adapt the POS experience without deep code changes.
- Support for multi-tasking and parallel workflows in the POS, enabling cashiers to handle multiple transactions or operations concurrently.
- Enhanced performance and responsiveness reduce friction during peak business hours.
- Comprehensive keyboard navigation and screen reader support improve accessibility compliance.
Benefits for Retailers
- Faster checkout processes increase customer satisfaction and reduce queues.
- Flexibility to innovate and customize POS functions helps differentiate the retail experience.
- Better accessibility opens the workforce pool and promotes inclusiveness.
For complete details and technical guidance, see the original Microsoft documentation:
Modern workflows in POS - Commerce | Dynamics 365
Improved handling of batch-tracked items
This documentation describes enhancements in Microsoft Dynamics 365 Commerce related to the processing of batch-tracked inventory items during the statement posting process. The improvements aim to ensure accurate tracking and handling of batch information to support inventory and financial operations.
Key points
- Context: When statements are posted in Dynamics 365 Commerce, batch-tracked items now have better handling mechanisms.
- Impact: This leads to more accurate recording of batch information in inventory transactions and ensures consistency between inventory and financial records.
- Improvement details:
- During statement posting, the system properly considers batch tracking for all related items.
- Batch numbers are maintained and reflected in postings, avoiding issues of lost or mismatched batch info.
- Enhances traceability and compliance, especially important for industries requiring batch control (e.g., pharmaceuticals, food, electronics).
Use and configuration
- These updates typically do not require manual configuration.
- Ensure that batch tracking is enabled and configured correctly on product records.
- Verify that statement posting processes are up to date with the latest Dynamics 365 Commerce updates to benefit from these improvements.
For more detailed technical steps or troubleshooting, refer to the official Microsoft documentation linked below.
Reference link:
https://learn.microsoft.com/en-us/dynamics365/commerce/batch
What's new or changed in the Warehouse Management mobile app
This article summarizes the new and updated features for each released version of the Warehouse Management app (WMA) for Microsoft Dynamics 365 Supply Chain Management. The WMA supports streamlined warehouse operations by optimizing task execution on mobile devices.
Key Highlights by Version
- New Features: Introduction of functionalities like enhanced barcode scanning, improved UI/UX, expanded device support, advanced task automation, and integration capabilities.
- Changes: Updates to workflows, bug fixes, performance improvements, and alignment with broader Dynamics 365 Supply Chain enhancements.
- Target Audience: Warehouse operators, logistics managers, and IT administrators using Dynamics 365 Supply Chain Management.
- Impact: Improves warehouse operation efficiency, accuracy, and mobile task execution.
Typical Areas of Update
| Feature Area | Description |
|---|---|
| Mobile device support | Added compatibility with new hardware and OS versions |
| Barcode scanning | Enhanced scanning stability and expanded barcode types |
| Task & workflow updates | Streamlined workflows for picking, putting, and packing |
| User interface | Improved responsiveness and usability |
| Integration | Better interoperability with Dynamics 365 modules |
| Performance | Reduced latency and increased reliability |
| Security | Updated authentication and data protection features |
How to Keep Updated
- Review version release notes regularly for detailed feature lists and bug fixes.
- Test new versions in controlled environments before deployment.
- Train warehouse users on new workflows and UI changes.
- Coordinate with Dynamics 365 Supply Chain support for troubleshooting and advice.
For complete details, including version-specific updates with dates and technical notes, please refer to the official Microsoft documentation:
Migrating the Warehouse Management Mobile App from V3 to V4 (Preview)
This article guides users on migrating from the Warehouse Management (WMS) mobile app version 3 (V3) to version 4 (V4) within Dynamics 365 Supply Chain Management. It covers compatibility considerations, prerequisites, and a recommended migration timeline.
Key Points
- Purpose: Transition from WMS mobile app V3 (older version) to the newer V4 release, which offers enhanced features and improved performance.
- Compatibility: V4 supports the latest platform capabilities and is intended for organizations looking to modernize their mobile warehouse operations.
- Requirements:
- Dynamics 365 Supply Chain Management must be updated to a version compatible with the WMS mobile app V4.
- Users should ensure all hardware and device OS versions support the new app version.
- Migration Timeline:
- Begin planning migration ahead of any planned deprecation of V3.
- Test the V4 app in a non-production environment before full rollout.
- Gradually roll out V4 across warehouse users to minimize disruption.
Migration Steps (Simplified)
- Assess Environment: Verify system versions and ensure compatibility with WMS mobile app V4.
- Prepare Devices: Update or acquire compatible devices supporting the V4 app.
- Setup and Configure V4:
- Install the WMS mobile app V4 from official sources.
- Configure required setup parameters in Dynamics 365 Supply Chain Management.
- Pilot Testing:
- Conduct functional testing in a test environment.
- Verify workflows and integrations.
- User Training: Educate warehouse staff on new features and differences in V4.
- Rollout:
- Deploy the app to production devices.
- Monitor adoption and address issues.
- Decommission V3: After successful migration, phase out the V3 app usage.
Additional Notes
- The migration is currently in preview, meaning some features might still be in refinement.
- It is recommended to regularly check official documentation for updates on support and new capabilities.
- Feedback from migration experiences can be submitted via Microsoft Dynamics 365 Ideas portal.
For detailed technical guidance, compatibility matrices, and configuration instructions, refer to the official documentation:
Release schedule for proactive quality updates (PQUs)
This article outlines the schedule and deployment methodology for proactive quality updates (PQUs) in Dynamics 365 Finance and Operations. PQUs are cumulative monthly updates designed to proactively improve product quality by addressing issues before customers encounter them. The updates are deployed via Microsoft-hosted environments following a structured station-to-region mapping model.
Key Information
- Update Frequency: Monthly PQUs released in the third week of each month.
- Deployment Flow: Updates roll out across multiple geographic stations, each mapped to one or more Azure regions.
- Station-to-Region Mapping: Each station represents a set of Azure regions. Updates complete on one station before deployment advances to the next.
- Update Scope: PQUs include fixes, performance improvements, and incremental capabilities that do not require extensive regression testing.
- Update Benefits: Early detection and remediation of issues to enhance system stability and user experience.
Station-to-Region Mapping Summary
| Station | Azure Regions Covered |
|---|---|
| 1 | US East, US East 2 |
| 2 | US Central, US West |
| 3 | UK South |
| 4 | Europe North, Europe West |
| 5 | Australia East, Australia Southeast |
| 6 | Asia East, Asia Southeast |
Note: This is an example; actual mappings can be found in the official documentation.
How PQUs Are Delivered
- PQUs are prepared and validated internally.
- Updates are released to the first station covering specific Azure regions.
- After validation in the first station, updates are progressively deployed to subsequent stations until all regions are updated.
- Customers using Dynamics 365 Finance and Operations in those regions receive automatic system updates with minimal business disruption.
Impact for Customers
- Customers benefit from faster and proactive fixes.
- Reduced downtime as updates are delivered with minimal interruption.
- Updates are fully managed by Microsoft in the cloud environment.
Additional Notes
- PQUs are separate from major feature updates and focus on proactive quality improvements.
- Customers can monitor update status via the service health dashboards.
- Detailed timelines and further region mappings are provided in the linked Microsoft documentation.
For further details, scheduling specifics, and region mappings, refer to the official Microsoft Learn article.
Original Article:
Release schedule for proactive quality updates - Finance & Operations | Dynamics 365