Environment update failed due to 'E-Document Core' extension – Field length reduction not allowed

(6) Share

Report

Posted on by PL-28101044-0

137

While attempting to update our Business Central SaaS environment from version 26.5.38752.38944 to 27.0.38460.39927, the operation failed due to an issue with the 'E-Document Core' extension version 27.0.38460.41225.

Error message:

The extension 'E-Document Core' failed to synchronize the database schema. Table 6101 E-Document Purchase Line :: The field '[BC] Item Reference No.' has reduced the data type length from '50' to '20'. Reducing the data type length of a field is not allowed.

This error prevents the entire environment update from completing successfully. Environment details:

Type: SaaS
Country/region: ES
Scheduled update: October 28, 2025
Start time: 10:44 CET
End time: 11:13 CET
Update status: Failed
Custom date selected: Yes

Question:

Is there an official fix or workaround for this issue in SaaS environments, where running Sync-NavApp is not possible?

Is Microsoft planning to release a corrected version of the 'E-Document Core' extension that avoids this schema conflict?

Any help or guidance would be greatly appreciated.

Categories:

Dynamics 365 Business Central

I have the same question (7)

All responses (9)

Answers (1)

Suggested answer

Sumit Singh 11,757 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hi, Below link might be related, waiting for fixation as per my understanding.

[Bug]: "[BC] Item Reference No." field length is too short. in E-Document Purchase Line · Issue #29009 · microsoft/ALAppExtensions

Was this reply helpful? Yes No
PL-28101044-0 137 on at

Like (3)

Report
Copy link

Link copied!
Hi Sumit,

Thanks for your support.

I’d like to better understand the behavior we’re seeing across different tenants. We’ve successfully updated some environments to version 27.0 where the E-Document Core extension is installed, and the update completed without any issues, even though the extension includes the same field length reduction.

However, in other environments — including some that do not actively use the E-Document module and have no records in table 6101 (E-Document Purchase Line) — the update is blocked due to the same schema conflict.

Could you please clarify:

Why the update proceeds successfully in some environments but fails in others, even when the extension is present?

Is there any way to bypass or defer the E-Document Core extension during the update process in environments where it's not used?

Is Microsoft planning to release a version of the extension that avoids this issue?

We’re trying to understand if there’s a workaround or configuration that allows the update to proceed safely in affected environments.

Thanks in advance for your help.

Best regards.

Was this reply helpful? Yes No
Suggested answer

Nimsara Jayathilaka. 4,950 Super User 2026 Season 1 on at

Like (7)

Report
Copy link

Link copied!

Hi

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/known-issues?wt.mc_id=DX-MVP-5004336#removed-tables-and-fields-in-the-e-document-core-extension-cause-synchronization-errors-on-upgrade

Was this reply helpful? Yes No
PL-28101044-0 137 on at

Like (3)

Report
Copy link

Link copied!
Hi Nimsara,

Thank you for sharing the workaround involving the Sync-NAVApp command with the ForceSync parameter.

However, our environment is SaaS, and we do not have access to the server instance or the ability to run PowerShell commands like Sync-NAVApp. As such, this workaround is only applicable to OnPrem environments, and unfortunately, it does not help us resolve the issue.

Could you please confirm:

If Microsoft is planning to release a corrected version of the E-Document Core extension that avoids this schema conflict in SaaS?

If there is any way to bypass or defer the update of this extension during the environment upgrade?

We’re currently blocked from upgrading due to this issue, even though the extension is not actively used in our environment.

Thanks again for your support.

Best regards.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 12,965 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

Hello,

Microsoft will release a corrected version of the extension.

Don’t retry the update manually, it will continue to fail.

Open a Microsoft support ticket referencing this known issue.

Monitor the Known Issues page for the fix.

Regards,

Oussama

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Rishabh Kanaskar 6,219 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi,

Yes, Microsoft has acknowledged the field‑length issue in E‑Document Core and marked it to ship in a future update. Monitor the GitHub issue #29009 for the release build. [Bug]: "[BC] Item Reference No." field length is too short. in E-Document Purchase Line · Issue #29009 · microsoft/ALAppExtensions

Thanks

Rishabh

Was this reply helpful? Yes No
PL-28101044-0 137 on at

Like (1)

Report
Copy link

Link copied!
Hi all,

Just to clarify: although GitHub issue #29009 is marked as resolved, I’m still experiencing the same error when trying to upgrade a SaaS environment with Spanish localization to version 27.0.

The error is not related to renaming values or modifying data at runtime, as described in the GitHub thread. In my case, the failure occurs during the upgrade process itself, even though:

The environment does not actively use the E-Document module.

There are no records in table 6101 E-Document Purchase Line.

The extension E-Document Core is installed as part of the standard localization package.

So while the GitHub issue may be resolved for the specific scenario of renaming long values, it does not cover upgrade failures in SaaS environments like mine, where the schema conflict still blocks the update.

Thanks for any further insights or confirmation if a corrected version of the extension is planned for SaaS upgrades.

Best regards.

Was this reply helpful? Yes No
PL-28101044-0 137 on at

Like (1)

Report
Copy link

Link copied!

Hi all,

Just a quick update — Microsoft has sent a message (see attached screenshot) that might be related to the issue I’m experiencing when upgrading a SaaS environment with Spanish localization to version 27.0.

If anyone has more details or confirmation that this message is linked to the current SaaS upgrade issue, I’d appreciate it.

Thanks.

Was this reply helpful? Yes No
Verified answer

Khushbu Rajvi. 22,130 Super User 2026 Season 1 on at

Like (3)

Report
Copy link

Link copied!

It’s very likely connected — the postponement message from Microsoft aligns with the same update wave where several tenants experienced upgrade-related problems.

1 people found this reply helpful.

Was this reply helpful? Yes No