Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | 
Jan 26, 2026 |
Mar 13, 2026 |
Business value
This feature adds a built‑in prerequisite check to help reduce failed, electronic reporting configuration imports and shorten the implementation time by providing early visibility of required prerequisites directly in the Configuration repository.
Instead of discovering missing dependencies after initiating an import, you can now proactively validate system requirements, including the required Dynamics 365 Finance application version, build number, and configuration dependencies, before importing a configuration version. This prevents avoidable errors, improves user confidence, and accelerates deployment of globalization and reporting updates across environments.
Feature details
This feature adds a built‑in prerequisite validation experience within the Configuration repository page. Before you import an electronic reporting (ER) configuration, you can verify that the system meets all required prerequisites for application version, build, and dependent configurations.
A new Prerequisites FastTab and a Check prerequisites action allow you to proactively confirm compatibility and avoid failed import attempts.
What’s new
Prerequisites FastTab added to the Configuration repository page.
Check prerequisites button validates:
- Required Finance application version
- Required platform build
- Required ER configuration dependencies
Improved error messages show explicit prerequisite gaps and guidance.
Import behavior is unchanged when all prerequisites are satisfied.
How it helps
- Reduces failed imports and troubleshooting loops.
- Gives implementers early visibility into configuration requirements.
- Supports smoother rollout of regulatory and globalization reporting updates.
- Saves time by resolving compatibility issues before beginning the import.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.