Update 27.1.202547.148809

Resolved an issue where changes to RecordID namespaces introduced in Business Central (BC) version 7 caused synchronization failures in the Global Master Data Sync app when syncing from BC27 to previous BC versions. This fix restores compatibility and ensures successful data transfer across environments.

Details:

• Microsoft changed the namespaces for RecordID fields in BC7, resulting in backward compatibility issues.

• When attempting to sync master data from a BC27 environment to a version prior to BC7, the sync would fail due to a namespace mismatch.

• This issue disrupted business processes that rely on consistent data across different BC environments.

Impact:

• Prevented successful synchronization of master data between BC27 and earlier versions.

• No known workaround was available prior to this fix.

Resolution:

• The synchronization logic has been updated to correctly handle RecordID namespaces, restoring compatibility between BC27 and earlier BC versions.

• If earlier version is onPrem and thus not updatable you can manually remove the Namespace Record ID via the below option (hidden field)

This update resolves a critical issue in the Global Master Data Sync (GMDS) app where operations involving data templates with obsolete or removed fields could cause failures or application crashes.

Details:

• The issue was triggered when Microsoft performed refactoring or when an app was uninstalled, resulting in fields being set to "removed" or deleted.

• Data template lines referencing these obsolete fields could cause errors during execution.

Resolution:

• The GMDS app now includes enhanced validation tests to ensure data integrity and prevent system failures when encountering obsolete fields.

• Improved error handling has been implemented to prevent application crashes.

• A cleanup function is now automatically activated whenever the global master is upgraded or data templates are released.

• A new report has been added to help clean up data template lines referencing obsolete fields.

Impact:

• Users will no longer experience forced closures or errors related to obsolete fields.

• The app is now compatible with the latest versions of Microsoft Dynamics 365 Business Central.

Resolved an issue where BLOB storage files, specifically the VN Country Master files, were not displaying and therefore not synchronizing to the partner system. Investigation revealed that the files were present in BLOB storage, but not visible or accessible as expected.

Root Cause:
The problem was traced to the large number of files stored in BLOB storage, which caused display and synchronization issues.

Analysis:
The issue was analyzed in collaboration with CEL, who is aware of the situation and its implications.

Next Steps:
We have ensured that the files are delivered correctly to the product.

Future Plans:
Please note that in a future release, we plan to adopt the new standard Business Central External File Storage to address such issues more robustly.