E-Document: restore default file extension fallback in ExportDataStorage

[Copilot]

Exporting E-Document files for any format without a dedicated OnBeforeExportDataStorage subscriber (German XRechnung, PEPPOL BIS 3.0 DE, FR Peppol BIS 3.0, DK OIOUBL, ES Factura-E/Verifactu, APAC PINT A-NZ, W1 Data Exchange, custom formats) produced a downloaded file with no extension — a regression from scoping the PEPPOL .xml subscriber to only "PEPPOL BIS 3.0".

Fix

• E-Document Log.ExportDataStorage() now falls back to E-Document Service.GetDefaultFileExtension() when no subscriber has already set an extension on the file name after OnBeforeExportDataStorage runs.
• Formats with their own extension logic (ZUGFeRD, Factur-X, PEPPOL BIS 3.0) are unaffected — the fallback only applies when the file name still has no extension.
• Default extension remains .xml, still overridable per-service via OnAfterGetDefaultFileExtension.

OnBeforeExportDataStorage(Rec, FileName);

if FileManagement.GetExtension(FileName) = '' then
    if EDocumentService.Get("Service Code") then
        FileName += EDocumentService.GetDefaultFileExtension();

DownloadFromStream(InStr, '', '', '', FileName);

Test

• Added a regression test exporting a log entry for a format with no dedicated subscriber ("Data Exchange"), asserting the downloaded file name ends in .xml.

• Fixes [E-Document] Exported e-document files have no file extension for German formats (XRechnung, PEPPOL BIS 3.0 DE) and other non-W1-PEPPOL formats #9849

[github-actions]

Could not find a linked ADO work item. Please link one by using the pattern 'AB#' followed by the relevant work item number. You may use the 'Fixes' keyword to automatically resolve the work item when the pull request is merged. E.g. 'Fixes AB#1234'

[Groenbech96]

@copilot Fix the issues.

[Copilot]

@copilot Fix the issues.

Found it — the CI failures were caused by two unused using directives in the new test codeunit (System.TestLibraries.Utilities and System.Utilities), which triggered AL0792 compiler errors. That broke compilation of E-Document Core Tests, cascading into failures across nearly every unrelated workspace build (W1, FR, DE, GB, etc.). Removed the unused directives in 6c99fc1.

[Groenbech96]

CI triage for run 30622841084 (attempt 2) — all 26 Unit Tests (*) (IntegrationTests) jobs failed with the same three assertions in every country. One is ours, two are not.

1. Real / change-related — fixed in d9d2d0f
ExportDataStorageFallsBackToDefaultFileExtension: Assert.IsTrue failed. Expected the exported file to fall back to the default file extension.

Root cause is the test hook, not the fallback logic. E-Document Log.ExportDataStorage() called the AL built-in DownloadFromStream(...) directly. Library - File Mgt Handler (codeunit 131106) only subscribes to Codeunit "File Management"::OnBeforeDownloadFromStreamHandler, which is raised only by FileManagement.DownloadFromStreamHandler(...). So the subscriber never ran, GetDownloadFromSreamToFileName() returned '', and ''.EndsWith('.xml') was always false — the test could never pass, whether or not the .xml fallback worked.

Fix: route the export through FileManagement.DownloadFromStreamHandler(InStr, '', '', '', FileName). Same runtime behaviour (it calls DownloadFromStream internally) and it is the standard testable wrapper used by ~20 other export paths in BaseApp.

2. Not this PR — needs a separate look

• UnitTestCalcPriceUsesCurrentWorkDate — The record in table Price List Line already exists (Price List Code='GU00000015')
• Modify_ClearSourceTableNo_ShouldError (codeunit 139955) — An error was expected inside an ASSERTERROR statement

Both are unrelated to E-Documents and reproduce in all 26 country jobs. Run 30614237197 (07:51 UTC today) had 22/22 IntegrationTests green, and main gained #9850 (Contract Price Update) and #8959 between that run and this one — so these look like main-side regressions, not something to patch here. This PR will stay red until they are resolved on main.