Version Numbering
Convention
Our versioning follows a specific pattern:
[MajorVersion].[MinVersion].[MaxVersion].[MinorVersion]
- MajorVersion: Major version number
- MinVersion: Minimum platform update supported, running a platform update below this version is not supported.
- MaxVersion: Maximum platform update supported, running a platform update above this version is not supported.
- MinorVersion: Changeset number, allows to uniquely identify source code.
Example
Version x.38.40.yyyy:
Is valid for D365 release 10.0.38, 10.0.39, 10.0.40,
Hasn't been tested against 10.0.37 and below,
Hasn't been tested against 10.0.41 and above.
Starting version 5.0, the warning messages will start appearing on non supported configurations:
Incorrect Data Upgrade
Why am I seeing this?
Data upgrade scripts have failed
Real life
Don't ignore Data upgrade scripts, make sure all scripts completed succesfully during upgrades.
Benefits
Data upgrade are designed to support software changes and opt-in features. If these are bypassed, we can't guarantee systems operations accordingly and may lead to issues or even data loss when features become deprecated.
Incorrect Version
When you see this message, please contact your administrator for code / data upgrades.
Please follow the prompts and Upgrade guide
Why am I seeing this?
This warning message means your D365 F&O version is not in sync with your eftsure inside D365 F&O version.
This likely occurs when your deployment team upgraded D365 F&O without upgrading eftsure inside D365 F&O.
If the D365 F&O version has been published after our eftsure inside D365 F&O version, we haven't been able to test the 2 versions together and therefore can't guarantee their compatibility.
Reach out to your deployment team and ask them to upgrade eftsure inside D365 F&O alongside D365 F&O
Real life
In most cases, the warning can be ignored and everything will continue to operate as expected.
However upgrades can inevitably break features over time, hence we maintain packages compatible with the last 3 versions at all times
We can't comment on out of sync versions as our internal tests haven't run on this combination (likely due to software availability at the time of testing).
We expect our customers to also upgrade, at least alongside each major D365 F&O versions, to ensure compatibility.
Benefits
Keeping all customers on recent versions is required to allow:
- Ends benefits from new features more frequently, projects get fixes & continuous improvements from other customers.
- Less support tickets (as old bug/fixes disappear within a maximum of 2 D365 releases - 12 months).
- Customers remain in support scope (deprecated versions might lead to internal/external/support costs).
- Support for latest eftsure api changes and features
- Support for latest partner solutions changes
- Support for new countries and related processes
- Support for latest Government code lookups and validations